← previous blocknext block →recent activity
Analyzing
Block #99,212,622
10 transactions · 10 stateful · 2026-08-26 02:43:04 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,212,622 · 10 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
1w03w04w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3bee222e…6158
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x631b4113…baa9
0x34b655…2a6f
4 touches
1 conflict
0x72a152dd…9de7
0x16f70c…c3dd
2 touches
0 conflicts
0x1aa85bda…e324
0x34b655…2a6f
2 touches
0 conflicts
0x26a96f1d…523f
0x34b655…2a6f
2 touches
0 conflicts
0x7b6d2deb…dde0
0x34b655…2a6f
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 0x3bee222e20…1d6158
Audit this contract →
← previous block·next block →recent activity