← previous blocknext block →recent activity
Analyzing
Block #104,325,942
15 transactions · 13 stateful · 2026-09-13 00:50:24 UTC
Parallelism
87/100
Blocked
23%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #104,325,942 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w012w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x17230b39…46bd
0x065c9d…c394
2 touches
0 conflicts
0xce827910…ff22
0x065c9d…c394
2 touches
0 conflicts
0xd591a1c1…15ef
0x065c9d…c394
2 touches
0 conflicts
0xda0cc240…e6f2
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
1 conflict on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity