← previous blocknext block →recent activity
Analyzing
Block #106,945,175
22 transactions · 21 stateful · 2026-09-22 04:55:07 UTC
Parallelism
82/100
Blocked
29%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,945,175 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w111w012w113w214w320w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x858e40c0…7e30
0x34b655…2a6f
8 touches
6 conflicts
0xeaf27f2a…e372
0x34b655…2a6f
8 touches
6 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
6 touches
3 conflicts
0x1f396cee…862f
0x34b655…2a6f
6 touches
3 conflicts
0xfe70049b…fa74
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0xade2f5e8…055a
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
6 conflicts on slot 0x858e40c022…9e7e30
Audit this contract →
← previous block·next block →recent activity