← previous blocknext block →recent activity
Analyzing
Block #99,211,130
14 transactions · 12 stateful · 2026-08-26 02:35:34 UTC
Parallelism
79/100
Blocked
25%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,211,130 · 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
1w02w05w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x6554e37e…6974
0x065c9d…c394
5 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xd3ee32c5…3498
0xd32edf…ff58
3 touches
1 conflict
0x16df9608…5922
0x065c9d…c394
2 touches
0 conflicts
0x348fda08…7e96
0x065c9d…c394
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x7cf60fab…8e6b
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
3 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity