← previous blocknext block →recent activity
Analyzing
Block #87,315,364
19 transactions · 18 stateful · 2026-07-12 17:36:07 UTC
Parallelism
79/100
Blocked
28%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,315,364 · 19 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
3w04w17w09w110w113w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3be33cca…0fff
0x34b655…2a6f
6 touches
3 conflicts
0x3be33cca…1000
0x34b655…2a6f
6 touches
3 conflicts
0x671703d0…94b1
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x543197bb…4f97
0x34b655…2a6f
4 touches
2 conflicts
0x65e6e603…cb45
0x34b655…2a6f
4 touches
1 conflict
0x71641e8d…a781
0x34b655…2a6f
4 touches
1 conflict
0x88f37d98…6792
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 0x3be33cca63…660fff
Audit this contract →
← previous block·next block →recent activity