← previous blocknext block →recent activity
Analyzing
Block #99,161,009
25 transactions · 19 stateful · 2026-08-25 22:23:25 UTC
Parallelism
84/100
Blocked
47%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,161,009 · 25 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
1w03w16w27w312w016w117w218w319w020w122w023w124w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xbd590df7…9891
0x34b655…2a6f
6 touches
3 conflicts
0x68531239…e9a3
0x34b655…2a6f
6 touches
3 conflicts
0x81d798a4…d8d2
0x065c9d…c394
5 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x4c29ecd5…58b6
0x34b655…2a6f
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
6 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity