← previous blocknext block →recent activity
Analyzing
Block #106,405,061
16 transactions · 16 stateful · 2026-09-20 07:35:38 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
1.31
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,405,061 · 16 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
2w03w14w27w28w39w410w514w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93ec9f85…b586
0x34b655…2a6f
12 touches
15 conflicts
0xd563f3a1…94b1
0x34b655…2a6f
12 touches
15 conflicts
0xb15c58ec…bd83
0x34b655…2a6f
10 touches
10 conflicts
0xa5811d93…8c73
0x34b655…2a6f
6 touches
3 conflicts
0xcb41ee48…d6bc
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xd1ed6c82…869d
0x34b655…2a6f
6 touches
3 conflicts
0x973b84cc…0613
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
15 conflicts on slot 0x93ec9f85d7…abb586
Audit this contract →
← previous block·next block →recent activity