← previous blocknext block →recent activity
Analyzing
Block #86,915,908
10 transactions · 9 stateful · 2026-07-10 21:05:44 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,915,908 · 10 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
1w02w14w05w16w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb76f7c01…c3a5
0x34b655…2a6f
4 touches
1 conflict
0xbf47a88f…7b7e
0x34b655…2a6f
4 touches
1 conflict
0xbf47a88f…7b7f
0x34b655…2a6f
4 touches
1 conflict
0xc50ac7d4…e964
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc948dbdc…199a
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xed660153…a905
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 0xb76f7c01e5…00c3a5
Audit this contract →
← previous block·next block →recent activity