← previous blocknext block →recent activity
Analyzing
Block #86,619,419
22 transactions · 17 stateful · 2026-07-09 12:03:28 UTC
Parallelism
68/100
Blocked
35%
Avg conflicts / tx
0.59
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,619,419 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w115w216w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xca2926e0…61b5
0x34b655…2a6f
6 touches
3 conflicts
0x42b8edbf…0cdd
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x59d2b543…5f66
0x34b655…2a6f
4 touches
1 conflict
0x92fcdf1e…23a7
0x34b655…2a6f
4 touches
1 conflict
0x9365e097…ff56
0x34b655…2a6f
4 touches
1 conflict
0xb409e204…89ac
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity