← previous blocknext block →recent activity
Analyzing
Block #86,790,347
24 transactions · 15 stateful · 2026-07-10 07:06:10 UTC
Parallelism
92/100
Blocked
33%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,790,347 · 24 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
1w07w08w110w112w013w116w018w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1a0d634…8c0d
0x34b655…2a6f
4 touches
1 conflict
0x8a35acfb…d1a8
0xb1dbf0…c0d3
4 touches
1 conflict
0x6c68ddc9…d106
0xb1dbf0…c0d3
4 touches
1 conflict
0xe1a1a29a…a399
0x34b655…2a6f
4 touches
1 conflict
0xe1a1a29a…a398
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xdc921364…4680
0x34b655…2a6f
4 touches
1 conflict
0x220f7734…6d97
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: Perpl
1 conflict on slot 0xb1a0d634af…958c0d
Audit this contract →
← previous block·next block →recent activity