← previous blocknext block →recent activity
Analyzing
Block #86,788,631
14 transactions · 12 stateful · 2026-07-10 06:54:45 UTC
Parallelism
79/100
Blocked
17%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,788,631 · 14 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
4w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1a8
0xb1dbf0…c0d3
6 touches
3 conflicts
0x6c68ddc9…d106
0xb1dbf0…c0d3
4 touches
1 conflict
0x6a248bdc…3c1b
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1a7
0xb1dbf0…c0d3
4 touches
1 conflict
0x7f430e47…4cbd
0xb1dbf0…c0d3
4 touches
1 conflict
0x17c3727d…cb0e
0x34b655…2a6f
2 touches
0 conflicts
0x20492d53…80f9
0x34b655…2a6f
2 touches
0 conflicts
0x6363986b…fe3a
0x34b655…2a6f
2 touches
0 conflicts
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
3 conflicts on slot 0x8a35acfbc1…6bd1a8
Audit this contract →
← previous block·next block →recent activity