← previous blocknext block →recent activity
Analyzing
Block #101,799,960
26 transactions · 20 stateful · 2026-09-04 04:01:07 UTC
Parallelism
85/100
Blocked
40%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,799,960 · 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
1w02w13w24w35w06w18w014w016w117w119w225w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe8f860c0…35c9
0x34b655…2a6f
8 touches
6 conflicts
0x3027f5b0…7a3f
0x34b655…2a6f
8 touches
6 conflicts
0x4f3cc09a…2804
0x34b655…2a6f
8 touches
6 conflicts
0x53e08444…d671
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0xb3e293fe…be2e
0x34b655…2a6f
8 touches
6 conflicts
0xb40e601f…bf98
0x34b655…2a6f
8 touches
6 conflicts
0xb826ef15…d248
0x34b655…2a6f
8 touches
6 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
6 conflicts on slot 0xe8f860c039…3435c9
Audit this contract →
← previous block·next block →recent activity