← previous blocknext block →recent activity
Analyzing
Block #102,743,449
19 transactions · 18 stateful · 2026-09-07 11:35:25 UTC
Parallelism
58/100
Blocked
44%
Avg conflicts / tx
1.21
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,743,449 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w112w213w314w415w516w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
14 touches
21 conflicts
0x0528ecf1…f176
0x065c9d…c394
13 touches
21 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
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
21 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity