← previous blocknext block →recent activity
Analyzing
Block #106,945,287
21 transactions · 20 stateful · 2026-09-22 04:55:41 UTC
Parallelism
71/100
Blocked
55%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,945,287 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w17w08w19w211w112w214w115w316w418w520w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdf562d2…9a05
0x34b655…2a6f
8 touches
6 conflicts
0x52b0b60a…f21e
0x34b655…2a6f
8 touches
6 conflicts
0x4ebd9eec…d5c3
0x34b655…2a6f
8 touches
6 conflicts
0x155e52ca…fac7
0x34b655…2a6f
6 touches
3 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x858e40c0…7e30
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xcdf562d2c5…c99a05
Audit this contract →
← previous block·next block →recent activity