← previous blocknext block →recent activity
Analyzing
Block #85,575,484
16 transactions · 11 stateful · 2026-07-04 15:55:01 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,575,484 · 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
1w02w03w110w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a63f4a4…fa9e
0x065c9d…c394
5 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0005
0x5e60bc…fe22
2 touches
0 conflicts
0x3d5a86d8…4b85
0x5e60bc…fe22
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 0x9a63f4a442…30fa9e
Audit this contract →
← previous block·next block →recent activity