← previous blocknext block →recent activity
Analyzing
Block #99,019,611
79 transactions · 74 stateful · 2026-08-25 10:27:05 UTC
Parallelism
96/100
Blocked
8%
Avg conflicts / tx
0.1
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,019,611 · 79 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
1w02w16w27w08w110w011w112w277w078w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x580e268c…203b
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xf8480e2a…dff5
0x1b6862…e19c
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x580e268c08…22203b
Audit this contract →
← previous block·next block →recent activity