← previous blocknext block →recent activity
Analyzing
Block #102,810,512
11 transactions · 11 stateful · 2026-09-07 17:15:56 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.55
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,810,512 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w08w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
4 touches
1 conflict
0xa605468c…1bfc
0x34ae4d…3fc5
4 touches
1 conflict
0x8046b62a…0ba4
0x34b655…2a6f
4 touches
1 conflict
0x4e366f4a…7a25
0x065c9d…c394
3 touches
1 conflict
0x002ac29a…80ff
0x065c9d…c394
2 touches
1 conflict
0x002ac29a…8100
0x065c9d…c394
2 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 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity