← previous blocknext block →recent activity
Analyzing
Block #99,182,384
14 transactions · 14 stateful · 2026-08-26 00:10:56 UTC
Parallelism
71/100
Blocked
21%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,182,384 · 14 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
3w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xb516316e…e48e
0x065c9d…c394
5 touches
3 conflicts
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0xc18a9693…3fa3
0x065c9d…c394
3 touches
1 conflict
0xa58e835e…9f7d
0x065c9d…c394
2 touches
0 conflicts
0xab4dc5b0…a545
0x065c9d…c394
2 touches
0 conflicts
0xba38536d…2b7d
0x065c9d…c394
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