← previous blocknext block →recent activity
Analyzing
Block #85,423,109
19 transactions · 17 stateful · 2026-07-03 23:00:34 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,423,109 · 19 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
1w02w13w24w35w06w17w28w311w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93c58e4d…9b32
0x336ed4…c59c
8 touches
6 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
0xc88f593e…5d93
0x336ed4…c59c
8 touches
6 conflicts
0x7b4f546f…15ad
0xd32edf…ff58
7 touches
6 conflicts
0x085c9fac…8fcf
0x8d1565…6723
6 touches
3 conflicts
0x47d4745e…02bb
0x336ed4…c59c
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: 0x336ed437…cfc59c
6 conflicts on slot 0x93c58e4dd7…459b32
Audit this contract →
← previous block·next block →recent activity