← previous blocknext block →recent activity
Analyzing
Block #105,627,392
23 transactions · 21 stateful · 2026-09-17 14:19:14 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,627,392 · 23 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
1w02w15w06w17w010w011w113w215w118w219w321w022w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61517790…ce3f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x678143da…dc6b
0x34b655…2a6f
6 touches
3 conflicts
0x4abcd6e1…47c9
0x34b655…2a6f
4 touches
1 conflict
0xf90c6521…d8f0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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 0x6151779006…58ce3f
Audit this contract →
← previous block·next block →recent activity