← previous blocknext block →recent activity
Analyzing
Block #86,616,574
21 transactions · 20 stateful · 2026-07-09 11:44:27 UTC
Parallelism
76/100
Blocked
45%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,616,574 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w39w010w112w215w016w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…000b
0x90c374…be45
8 touches
6 conflicts
0x00000000…000a
0x90c374…be45
8 touches
6 conflicts
0x10a2bd5d…ad6d
0x8d1565…6723
8 touches
6 conflicts
0x93c58e4d…9b32
0x336ed4…c59c
8 touches
6 conflicts
0xc9e07b63…930d
0x34b655…2a6f
6 touches
3 conflicts
0x47d4745e…02bb
0x336ed4…c59c
6 touches
3 conflicts
0x085df2c1…305a
0x34b655…2a6f
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity