← previous blocknext block →recent activity
Analyzing
Block #99,210,189
17 transactions · 12 stateful · 2026-08-26 02:30:50 UTC
Parallelism
82/100
Blocked
25%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,210,189 · 17 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
3w04w112w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f65b82a…676b
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x384c3f6d…7fab
0x065c9d…c394
3 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x14d15259…7553
0x2b46c0…1669
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
1 conflict on slot 0x8f65b82ab2…75676b
Audit this contract →
← previous block·next block →recent activity