← previous blocknext block →recent activity
Analyzing
Block #102,309,926
30 transactions · 23 stateful · 2026-09-05 23:02:40 UTC
Parallelism
77/100
Blocked
35%
Avg conflicts / tx
0.73
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,309,926 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w37w08w422w523w024w126w527w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
12 touches
15 conflicts
0x342f4b45…c395
0x065c9d…c394
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x21169b82…a5df
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x44d7acbf…e67b
0x1b6862…e19c
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
15 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity