← previous blocknext block →recent activity
Analyzing
Block #106,471,515
18 transactions · 17 stateful · 2026-09-20 13:10:09 UTC
Parallelism
83/100
Blocked
35%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,471,515 · 18 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
1w02w14w05w16w08w210w011w114w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x22659874…ec0b
0x34b655…2a6f
4 touches
1 conflict
0x2559451e…537d
0x34b655…2a6f
4 touches
1 conflict
0x2ca8f610…cee3
0x34b655…2a6f
4 touches
1 conflict
0x2f50c84a…3640
0x34b655…2a6f
4 touches
1 conflict
0x3c70ac8d…eaf2
0x34b655…2a6f
4 touches
1 conflict
0x5ad5e6de…e7ad
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
3 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity