← previous blocknext block →recent activity
Analyzing
Block #87,576,390
16 transactions · 13 stateful · 2026-07-13 22:42:34 UTC
Parallelism
75/100
Blocked
54%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,576,390 · 16 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
1w02w03w15w06w17w28w19w314w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x07f69062…03ec
0x34b655…2a6f
4 touches
1 conflict
0x14bf5abe…91f5
0x34b655…2a6f
4 touches
1 conflict
0x3d22c439…de6d
0x34b655…2a6f
4 touches
1 conflict
0x461428a9…24b2
0x34b655…2a6f
4 touches
1 conflict
0x461428a9…24b3
0x34b655…2a6f
4 touches
1 conflict
0x469e26f1…62ec
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity