← previous blocknext block →recent activity
Analyzing
Block #87,361,407
19 transactions · 19 stateful · 2026-07-12 22:44:00 UTC
Parallelism
63/100
Blocked
58%
Avg conflicts / tx
0.89
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,361,407 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w05w16w29w310w411w512w214w617w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc3f7ee8…7924
0x34b655…2a6f
8 touches
6 conflicts
0x16b3a441…13db
0x34b655…2a6f
6 touches
3 conflicts
0x73066c00…1bfd
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x7506443a…4820
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xa457c06e…2f06
0x34b655…2a6f
6 touches
3 conflicts
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
6 conflicts on slot 0xcc3f7ee8e4…307924
Audit this contract →
← previous block·next block →recent activity