← previous blocknext block →recent activity
Analyzing
Block #102,649,693
11 transactions · 9 stateful · 2026-09-07 03:43:43 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,649,693 · 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
5w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea0d4e01…6bf6
0x34b655…2a6f
4 touches
1 conflict
0x1867b653…e61b
0x34b655…2a6f
4 touches
1 conflict
0x247cfb80…cca8
0x34b655…2a6f
4 touches
1 conflict
0x811ef74b…2a39
0x34b655…2a6f
4 touches
1 conflict
0x0525f5a2…6bab
0x34b655…2a6f
2 touches
0 conflicts
0x1513b999…b52e
0x34b655…2a6f
2 touches
0 conflicts
0x54379e71…5bf0
0x34b655…2a6f
2 touches
0 conflicts
0x18fd28b5…20c6
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xea0d4e011d…876bf6
Audit this contract →
← previous block·next block →recent activity