← previous blocknext block →recent activity
Analyzing
Block #99,181,422
33 transactions · 19 stateful · 2026-08-26 00:06:06 UTC
Parallelism
79/100
Blocked
47%
Avg conflicts / tx
0.64
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,181,422 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w08w09w111w214w315w416w519w129w630w532w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0xba38536d…2b7d
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0x6f0b9c02…1b90
0xa6afd3…d132
5 touches
3 conflicts
0x266bcb29…e6a8
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0002
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
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
10 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity