← previous blocknext block →recent activity
Analyzing
Block #102,809,211
19 transactions · 15 stateful · 2026-09-07 17:09:21 UTC
Parallelism
68/100
Blocked
60%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,809,211 · 19 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
1w02w15w26w07w28w314w415w116w217w518w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb87af72a…aef6
0x2a68ba…90c5
6 touches
3 conflicts
0xc4ed3294…3ac3
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xd075e9ec…78a8
0xd32edf…ff58
5 touches
3 conflicts
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x91ecc547…33ee
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
3 conflicts on slot 0xb87af72ae5…0baef6
Audit this contract →
← previous block·next block →recent activity