← previous blocknext block →recent activity
Analyzing
Block #101,670,783
17 transactions · 16 stateful · 2026-09-03 17:11:24 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,670,783 · 17 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
1w02w13w210w011w112w013w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
6 touches
3 conflicts
0xe9cae1b1…8ea7
0x34b655…2a6f
6 touches
3 conflicts
0x1c3c07cc…aa96
0x34b655…2a6f
4 touches
1 conflict
0x27e96819…bc58
0x34b655…2a6f
4 touches
1 conflict
0x46da8333…743c
0x34b655…2a6f
4 touches
1 conflict
0x4babcbd0…e24c
0x34b655…2a6f
4 touches
1 conflict
0x56e0d685…c960
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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity