← previous blocknext block →recent activity
Analyzing
Block #101,308,693
29 transactions · 24 stateful · 2026-09-02 10:49:36 UTC
Parallelism
90/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,308,693 · 29 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
6w08w011w012w113w014w115w221w123w226w027w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x706c758c…2fdb
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xe2e98890…0571
0x34b655…2a6f
4 touches
1 conflict
0x91ca1434…4017
0x34b655…2a6f
4 touches
1 conflict
0xb5cddf91…0abf
0x34b655…2a6f
4 touches
1 conflict
0xc5847c4d…a65c
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
3 conflicts on slot 0x706c758c00…e62fdb
Audit this contract →
← previous block·next block →recent activity