← previous blocknext block →recent activity
Analyzing
Block #86,978,792
13 transactions · 11 stateful · 2026-07-11 04:05:52 UTC
Parallelism
69/100
Blocked
45%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,978,792 · 13 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
1w02w03w14w05w18w29w310w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d1bb389…c7d9
0xb1dbf0…c0d3
4 touches
1 conflict
0x0335ae80…8414
0xb1dbf0…c0d3
4 touches
1 conflict
0x74825c4e…32e9
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d19e
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1ab
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1ac
0xb1dbf0…c0d3
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
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: 0xb1dbf05f…b1c0d3
1 conflict on slot 0x9d1bb3891b…cac7d9
Audit this contract →
← previous block·next block →recent activity