← previous blocknext block →recent activity
Analyzing
Block #86,531,751
11 transactions · 8 stateful · 2026-07-09 02:15:39 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,531,751 · 11 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
0x80a736f3…3442
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1a6
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1a7
0xb1dbf0…c0d3
4 touches
1 conflict
0xf07207b3…cefc
0xb1dbf0…c0d3
4 touches
1 conflict
0x1cff8072…13a4
0x34b655…2a6f
2 touches
0 conflicts
0x51a914cf…a822
0x34b655…2a6f
2 touches
0 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
2 touches
0 conflicts
0x7ee6007b…fd68
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 0x80a736f370…0a3442
Audit this contract →
← previous block·next block →recent activity