← previous blocknext block →recent activity
Analyzing
Block #102,480,727
14 transactions · 14 stateful · 2026-09-06 13:28:00 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,480,727 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w19w010w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c67d31e…3dbe
0x34b655…2a6f
6 touches
3 conflicts
0x90b26001…4012
0x34b655…2a6f
4 touches
1 conflict
0x22f10271…841d
0x34b655…2a6f
4 touches
1 conflict
0x9a7631b1…4f23
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6ca0994e…02ef
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
3 conflicts on slot 0x3c67d31e03…f03dbe
Audit this contract →
← previous block·next block →recent activity