← previous blocknext block →recent activity
Analyzing
Block #87,284,052
24 transactions · 20 stateful · 2026-07-12 14:06:48 UTC
Parallelism
92/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,284,052 · 24 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w16w07w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc3f7ee8…7924
0x34b655…2a6f
4 touches
1 conflict
0xd11cb968…7655
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x034d14da…9f5f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x44231245…5442
0x34b655…2a6f
4 touches
1 conflict
0x4864a33e…4a1d
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 0xcc3f7ee8e4…307924
Audit this contract →
← previous block·next block →recent activity