← previous blocknext block →recent activity
Analyzing
Block #86,741,289
18 transactions · 17 stateful · 2026-07-10 01:38:35 UTC
Parallelism
72/100
Blocked
29%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,741,289 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w410w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1ac
0xb1dbf0…c0d3
10 touches
10 conflicts
0x8a35acfb…d1ab
0xb1dbf0…c0d3
8 touches
6 conflicts
0x80a736f3…3442
0xb1dbf0…c0d3
6 touches
3 conflicts
0xf07207b3…cefc
0xb1dbf0…c0d3
6 touches
3 conflicts
0x5ed58b36…c5e5
0x34b655…2a6f
4 touches
1 conflict
0x6891580e…b028
0x34b655…2a6f
4 touches
1 conflict
0x78346476…4311
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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: 0xb1dbf05f…b1c0d3
10 conflicts on slot 0x8a35acfbc1…6bd1ac
Audit this contract →
← previous block·next block →recent activity