← previous blocknext block →recent activity
Analyzing
Block #87,305,267
10 transactions · 8 stateful · 2026-07-12 16:28:36 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,305,267 · 10 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
2w03w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x17c59430…544b
0x34b655…2a6f
4 touches
1 conflict
0x1ba5d36c…9336
0x34b655…2a6f
4 touches
1 conflict
0x1c978e6f…37e4
0x34b655…2a6f
4 touches
1 conflict
0x4cd4097b…c64b
0x34b655…2a6f
4 touches
1 conflict
0x6c7b899c…70ff
0x34b655…2a6f
4 touches
1 conflict
0x6c7b899c…7100
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity