← previous blocknext block →recent activity
Analyzing
Block #87,319,480
9 transactions · 8 stateful · 2026-07-12 18:03:38 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,319,480 · 9 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
1w02w14w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x974c36fe…1cd7
0x34b655…2a6f
6 touches
3 conflicts
0x59e84008…7fad
0x34b655…2a6f
4 touches
1 conflict
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xccba0904…3fa5
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x98f1477e…f3d9
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x59e84008…7fac
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 0x974c36fe03…4f1cd7
Audit this contract →
← previous block·next block →recent activity