← previous blocknext block →recent activity
Analyzing
Block #86,048,018
23 transactions · 21 stateful · 2026-07-06 20:25:25 UTC
Parallelism
74/100
Blocked
33%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,048,018 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w011w113w014w116w017w118w219w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x26adbb9b…4a02
0x34b655…2a6f
4 touches
1 conflict
0x31394eaa…89c5
0x34b655…2a6f
4 touches
1 conflict
0x3147083e…48d9
0x34b655…2a6f
4 touches
1 conflict
0x63ce81c4…c889
0x34b655…2a6f
4 touches
1 conflict
0x8f3113c5…dbc4
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity