← previous blocknext block →recent activity
Analyzing
Block #86,627,387
18 transactions · 16 stateful · 2026-07-09 12:56:37 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,627,387 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w09w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
6 touches
3 conflicts
0x93c58e4d…9b32
0x336ed4…c59c
4 touches
1 conflict
0xc88f593e…5d93
0x336ed4…c59c
4 touches
1 conflict
0x00000000…000b
0x90c374…be45
4 touches
1 conflict
0x47d4745e…02bb
0x336ed4…c59c
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
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
3 conflicts on slot 0x1941b4413e…0c5889
Audit this contract →
← previous block·next block →recent activity