← previous blocknext block →recent activity
Analyzing
Block #104,032,844
58 transactions · 30 stateful · 2026-09-12 00:01:22 UTC
Parallelism
81/100
Blocked
70%
Avg conflicts / tx
1.16
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #104,032,844 · 58 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w48w511w612w713w847w151w954w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
18 touches
36 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xce827910…ff22
0x065c9d…c394
8 touches
6 conflicts
0x3e1e8e54…9c83
0x2a68ba…90c5
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x213ee207…a151
0x34ae4d…3fc5
8 touches
6 conflicts
0x46279ae7…20dd
0x34ae4d…3fc5
8 touches
6 conflicts
0x53e50026…6d8c
0x34ae4d…3fc5
8 touches
6 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
36 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity