← previous blocknext block →recent activity
Analyzing
Block #86,240,004
26 transactions · 19 stateful · 2026-07-07 17:46:46 UTC
Parallelism
85/100
Blocked
37%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,240,004 · 26 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
2w03w16w07w118w219w120w221w324w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd98a779…23ee
0x40c49f…2af0
6 touches
3 conflicts
0xbcdee322…f454
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x006ee1d9…5485
0xa6afd3…d132
4 touches
1 conflict
0x76d1e78d…7877
0x40c49f…2af0
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xb3a808ac…2bac
0x40c49f…2af0
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: 0x40c49f17…d22af0
3 conflicts on slot 0xcd98a779d5…5723ee
Audit this contract →
← previous block·next block →recent activity