← previous blocknext block →recent activity
Analyzing
Block #106,950,491
22 transactions · 20 stateful · 2026-09-22 05:21:52 UTC
Parallelism
91/100
Blocked
15%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,950,491 · 22 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w011w012w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6ca15e14…7be8
0x34b655…2a6f
4 touches
1 conflict
0x37ad906a…ae75
0x34b655…2a6f
2 touches
0 conflicts
0x385d548d…ad18
0x34b655…2a6f
2 touches
0 conflicts
0x4f4a6267…4dc6
0x34b655…2a6f
2 touches
0 conflicts
0x61f82fb7…993d
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
1 conflict on slot 0x49b9fdd5ff…6f9c16
Audit this contract →
← previous block·next block →recent activity