← previous blocknext block →recent activity
Analyzing
Block #106,034,655
20 transactions · 17 stateful · 2026-09-19 00:31:28 UTC
Parallelism
85/100
Blocked
41%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,034,655 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w16w19w113w214w118w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x566d7924…8385
0x34b655…2a6f
6 touches
3 conflicts
0x39561c15…c70f
0x34b655…2a6f
6 touches
3 conflicts
0x3823a798…22aa
0x34b655…2a6f
4 touches
1 conflict
0xc4c74438…20e5
0xc8689a…ee79
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…004f
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x1adde00d…ed31
0xa6afd3…d132
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 0x566d792404…9a8385
Audit this contract →
← previous block·next block →recent activity