← previous blocknext block →recent activity
Analyzing
Block #99,209,704
12 transactions · 12 stateful · 2026-08-26 02:28:23 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,209,704 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w18w29w310w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x59a5cd57…0f7b
0x065c9d…c394
5 touches
3 conflicts
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x80df37e3…3f49
0xd32edf…ff58
3 touches
1 conflict
0x0fd5f9da…1e9b
0x34b655…2a6f
2 touches
0 conflicts
0x126c10ea…a328
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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: MarginAccount
6 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity