← previous blocknext block →recent activity
Analyzing
Block #101,321,599
14 transactions · 11 stateful · 2026-09-02 11:54:32 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,321,599 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w08w210w311w413w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x676b5eb4…0b33
0x34b655…2a6f
6 touches
3 conflicts
0xbb975a6c…bff4
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0xad7634f3…828b
0x34b655…2a6f
4 touches
1 conflict
0xd4c913d7…343d
0x1b6862…e19c
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 0x676b5eb480…240b33
Audit this contract →
← previous block·next block →recent activity