← previous blocknext block →recent activity
Analyzing
Block #85,904,130
18 transactions · 14 stateful · 2026-07-06 04:24:53 UTC
Parallelism
72/100
Blocked
50%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,904,130 · 18 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
1w02w13w24w35w46w09w111w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10a2bd5d…ad6d
0x8d1565…6723
10 touches
10 conflicts
0x00000000…000b
0x90c374…be45
10 touches
10 conflicts
0x00000000…000a
0x90c374…be45
10 touches
10 conflicts
0x34443913…cbf3
0x336ed4…c59c
8 touches
6 conflicts
0x006e55b1…660f
0x8d1565…6723
6 touches
3 conflicts
0x4a870d86…79ef
0x336ed4…c59c
6 touches
3 conflicts
0x47d4745e…02bb
0x336ed4…c59c
6 touches
3 conflicts
0xb274cb13…808b
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: 0x8d156514…236723
10 conflicts on slot 0x10a2bd5d43…51ad6d
Audit this contract →
← previous block·next block →recent activity