← previous blocknext block →recent activity
Analyzing
Block #86,715,445
7 transactions · 6 stateful · 2026-07-09 22:45:51 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,715,445 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a248bdc…3c1b
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1a7
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1a8
0xb1dbf0…c0d3
4 touches
1 conflict
0xb07a0849…3b62
0xb1dbf0…c0d3
4 touches
1 conflict
0x2fead171…13d6
0x34b655…2a6f
2 touches
0 conflicts
0x40287836…2dff
0x34b655…2a6f
2 touches
0 conflicts
0x40883ce5…2ae2
0x34b655…2a6f
2 touches
0 conflicts
0x6083af24…a0df
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
1 conflict on slot 0x6a248bdcb5…023c1b
Audit this contract →
← previous block·next block →recent activity