← previous blocknext block →recent activity
Analyzing
Block #99,203,792
14 transactions · 13 stateful · 2026-08-26 01:58:39 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,203,792 · 14 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
1w02w13w14w210w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x81ca8c9e…28cb
0x34b655…2a6f
4 touches
1 conflict
0xb1856468…e84f
0x34b655…2a6f
4 touches
1 conflict
0xb6fcbbb7…2b31
0x34b655…2a6f
4 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
2 touches
0 conflicts
0xb4f1fea1…8443
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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
3 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity