← previous blocknext block →recent activity
Analyzing
Block #87,315,236
11 transactions · 11 stateful · 2026-07-12 17:35:16 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,315,236 · 11 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
2w03w15w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64aaadbf…f9f3
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x671703d0…94b1
0x34b655…2a6f
4 touches
1 conflict
0x79ad9283…5fd1
0x34b655…2a6f
4 touches
1 conflict
0x9cf61590…ad8c
0x34b655…2a6f
4 touches
1 conflict
0xa3c36de0…3cf3
0x34b655…2a6f
4 touches
1 conflict
0xc6d563ee…1268
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
3 conflicts on slot 0x64aaadbf0a…79f9f3
Audit this contract →
← previous block·next block →recent activity