← previous blocknext block →recent activity
Analyzing
Block #106,950,412
13 transactions · 12 stateful · 2026-09-22 05:21:29 UTC
Parallelism
77/100
Blocked
17%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,950,412 · 13 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
1w02w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xeb179a44…5477
0x34b655…2a6f
4 touches
1 conflict
0x8f18c248…9da5
0x34b655…2a6f
4 touches
1 conflict
0xae85d138…81ab
0x34b655…2a6f
4 touches
1 conflict
0x5fad6fee…7714
0x34b655…2a6f
4 touches
1 conflict
0x23769ebc…c8ed
0x34b655…2a6f
2 touches
0 conflicts
0x4cb4372c…155e
0x34b655…2a6f
2 touches
0 conflicts
0x6c26d635…1bbf
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
3 conflicts on slot 0x49b9fdd5ff…6f9c16
Audit this contract →
← previous block·next block →recent activity