← previous blocknext block →recent activity
Analyzing
Block #87,576,181
14 transactions · 11 stateful · 2026-07-13 22:41:10 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,576,181 · 14 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
2w03w16w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04c1786f…3ee6
0x34b655…2a6f
4 touches
1 conflict
0x07f69062…03ec
0x34b655…2a6f
4 touches
1 conflict
0x0d64bba6…c643
0x34b655…2a6f
4 touches
1 conflict
0x0dcb313d…7073
0x34b655…2a6f
4 touches
1 conflict
0x17c70f19…23a7
0x34b655…2a6f
4 touches
1 conflict
0x20a110e8…918d
0x34b655…2a6f
4 touches
1 conflict
0x21158693…63e2
0x34b655…2a6f
4 touches
1 conflict
0x2274cf9c…3c78
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
1 conflict on slot 0x04c1786f74…073ee6
Audit this contract →
← previous block·next block →recent activity