← previous blocknext block →recent activity
Analyzing
Block #101,309,084
11 transactions · 11 stateful · 2026-09-02 10:51:34 UTC
Parallelism
36/100
Blocked
64%
Avg conflicts / tx
2
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,309,084 · 11 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w36w47w58w610w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00f6a8a7…0e6e
0x34b655…2a6f
2 touches
0 conflicts
0x1c255088…e409
0x34b655…2a6f
2 touches
0 conflicts
0x1ec65367…3705
0x34b655…2a6f
2 touches
0 conflicts
0x22731395…25d8
0x34b655…2a6f
2 touches
0 conflicts
0x2a58d502…385c
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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity