← previous blocknext block →recent activity
Analyzing
Block #99,586,235
30 transactions · 25 stateful · 2026-08-27 10:06:35 UTC
Parallelism
90/100
Blocked
44%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,586,235 · 30 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
1w02w03w04w17w08w19w110w011w116w019w120w121w222w224w025w127w028w129w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x4761ac57…c42c
0xa6afd3…d132
4 touches
1 conflict
0xdf08af9e…1985
0xa6afd3…d132
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x24c2a068…58af
0x34b655…2a6f
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity