← previous blocknext block →recent activity
Analyzing
Block #86,678,942
22 transactions · 19 stateful · 2026-07-09 18:42:14 UTC
Parallelism
82/100
Blocked
37%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,678,942 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w010w113w218w219w320w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x459573ed…fbbe
0x34b655…2a6f
6 touches
3 conflicts
0x61d831a8…f105
0xd32edf…ff58
5 touches
3 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd4cd86bf…44e3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdf4f5752…f6e6
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
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
3 conflicts on slot 0x459573ed17…94fbbe
Audit this contract →
← previous block·next block →recent activity