← previous blocknext block →recent activity
Analyzing
Block #102,042,284
18 transactions · 15 stateful · 2026-09-05 00:26:06 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,042,284 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w111w015w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0480f80d…7213
0x34b655…2a6f
4 touches
1 conflict
0x049bef37…1996
0x34b655…2a6f
4 touches
1 conflict
0x33b7fbba…64de
0x34b655…2a6f
4 touches
1 conflict
0x3d13406e…eff1
0x34b655…2a6f
4 touches
1 conflict
0x477cb4f5…11b4
0x34b655…2a6f
4 touches
1 conflict
0x4dffc33e…068d
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x5d4d66d1…f755
0x34b655…2a6f
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
1 conflict on slot 0x0480f80ddf…5b7213
Audit this contract →
← previous block·next block →recent activity