← previous blocknext block →recent activity
Analyzing
Block #85,849,116
16 transactions · 15 stateful · 2026-07-05 22:18:30 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,849,116 · 16 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
1w02w13w28w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xe3f3328d…bb35
0x065c9d…c394
4 touches
1 conflict
0xb1f0701d…4f4a
0xc8689a…ee79
4 touches
1 conflict
0xf11e8bcd…a3d6
0x065c9d…c394
4 touches
1 conflict
0xcd893742…30a4
0x065c9d…c394
3 touches
1 conflict
0x9e1c7b1d…25ea
0x065c9d…c394
3 touches
1 conflict
0x30d18ce3…5123
0x065c9d…c394
2 touches
0 conflicts
0x3698f416…2833
0x065c9d…c394
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity