← previous blocknext block →recent activity
Analyzing
Block #86,075,049
16 transactions · 13 stateful · 2026-07-06 23:25:41 UTC
Parallelism
81/100
Blocked
23%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,075,049 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w010w111w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x6176d66d…5404
0x065c9d…c394
4 touches
1 conflict
0x44b51603…03b5
0x065c9d…c394
3 touches
1 conflict
0x778a8174…d00d
0x065c9d…c394
3 touches
1 conflict
0xc6f1b3af…c97c
0x1001ff…1001
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity