← previous blocknext block →recent activity
Analyzing
Block #102,800,657
26 transactions · 24 stateful · 2026-09-07 16:26:17 UTC
Parallelism
85/100
Blocked
42%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,800,657 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w07w28w310w214w015w118w119w220w325w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33000c0a…82c3
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x6518075e…2b17
0x2a68ba…90c5
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x065ff70b…356d
0x40c49f…2af0
5 touches
3 conflicts
0x5158bba9…dddb
0x34b655…2a6f
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: Perpl
6 conflicts on slot 0x33000c0a30…f582c3
Audit this contract →
← previous block·next block →recent activity