← previous blocknext block →recent activity
Analyzing
Block #106,955,500
24 transactions · 21 stateful · 2026-09-22 05:47:05 UTC
Parallelism
92/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,955,500 · 24 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
1w02w06w18w09w110w011w012w114w116w017w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
0x34b655…2a6f
4 touches
1 conflict
0x66b19827…9edc
0x34b655…2a6f
4 touches
1 conflict
0x6ae47f75…7b45
0x34b655…2a6f
4 touches
1 conflict
0x87922600…0ec2
0x34b655…2a6f
4 touches
1 conflict
0x91cd366d…5cea
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
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
1 conflict on slot 0x49b9fdd5ff…6f9c16
Audit this contract →
← previous block·next block →recent activity