← previous blocknext block →recent activity
Analyzing
Block #86,883,201
22 transactions · 19 stateful · 2026-07-10 17:27:09 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
0.73
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,883,201 · 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
4w05w16w210w011w314w118w319w420w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x636fd21a…9978
0x34b655…2a6f
8 touches
6 conflicts
0x5b813b1d…5968
0x34b655…2a6f
8 touches
6 conflicts
0x5261c6c4…007f
0x34b655…2a6f
6 touches
3 conflicts
0x5472ed41…6309
0x34b655…2a6f
6 touches
3 conflicts
0x54d813ad…0dec
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 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: Perpl
6 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity