← previous blocknext block →recent activity
Analyzing
Block #106,235,069
27 transactions · 22 stateful · 2026-09-19 17:20:11 UTC
Parallelism
81/100
Blocked
27%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,235,069 · 27 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
1w03w14w06w17w09w211w312w415w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf99856c4…370d
0x34b655…2a6f
10 touches
10 conflicts
0x34fb061c…1b55
0x34b655…2a6f
8 touches
6 conflicts
0x755c7b95…9404
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x05e1eba1…6491
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
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
10 conflicts on slot 0xf99856c491…9a370d
Audit this contract →
← previous block·next block →recent activity