← previous blocknext block →recent activity
Analyzing
Block #102,040,250
31 transactions · 24 stateful · 2026-09-05 00:15:48 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,040,250 · 31 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w26w37w08w39w012w417w020w124w527w028w129w030w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x77ed432f…fa04
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xde92af2a…a316
0x065c9d…c394
5 touches
3 conflicts
0xb87af72a…aef6
0x2a68ba…90c5
4 touches
1 conflict
0x06e40499…165e
0x34ae4d…3fc5
4 touches
1 conflict
0x48ed1159…abe9
0x34ae4d…3fc5
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 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity