← previous blocknext block →recent activity
Analyzing
Block #86,672,331
18 transactions · 14 stateful · 2026-07-09 17:58:08 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,672,331 · 18 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
2w04w05w16w07w19w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6101b5d…4361
0x3bd359…433a
4 touches
1 conflict
0xa164d951…1534
0xe1c8b7…3022
4 touches
1 conflict
0x00000000…0004
0x48c3bb…b17b
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x95d63682…276c
0x34b655…2a6f
4 touches
1 conflict
0x95d63682…276d
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: Wrapped MON (WMON)
1 conflict on slot 0xc6101b5dc8…d04361
Audit this contract →
← previous block·next block →recent activity