← previous blocknext block →recent activity
Analyzing
Block #86,790,162
20 transactions · 19 stateful · 2026-07-10 07:04:56 UTC
Parallelism
85/100
Blocked
26%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,790,162 · 20 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
1w02w03w17w08w19w110w217w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce3cd522…e49d
0x34b655…2a6f
4 touches
1 conflict
0xbf863077…06c5
0x34b655…2a6f
4 touches
1 conflict
0xbf863077…06c6
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x167de262…f61f
0x34b655…2a6f
4 touches
1 conflict
0x2d94ecd9…43db
0x34b655…2a6f
4 touches
1 conflict
0x461428a9…24b2
0x34b655…2a6f
4 touches
1 conflict
0x461428a9…24b3
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 0xce3cd522d6…71e49d
Audit this contract →
← previous block·next block →recent activity