← previous blocknext block →recent activity
Analyzing
Block #94,058,456
8 transactions · 6 stateful · 2026-08-08 00:05:53 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,058,456 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96076fe1…8538
0xa6afd3…d132
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xaf831072…51d5
0x69a5f9…2fef
2 touches
0 conflicts
0xaf831072…51d6
0x69a5f9…2fef
2 touches
0 conflicts
0xaf831072…51d7
0x69a5f9…2fef
2 touches
0 conflicts
0xaf831072…51dc
0x69a5f9…2fef
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-WETH/USDC
1 conflict on slot 0x96076fe141…c18538
Audit this contract →
← previous block·next block →recent activity