← previous blocknext block →recent activity
Analyzing
Block #106,933,981
20 transactions · 19 stateful · 2026-09-22 03:58:46 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
1.2
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,933,981 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w07w08w19w210w311w412w513w616w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe720a4c6…8eb0
0x34b655…2a6f
14 touches
21 conflicts
0xba1edffb…323e
0x34b655…2a6f
14 touches
21 conflicts
0x3780a34a…b50a
0x34b655…2a6f
14 touches
21 conflicts
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xce307d4a…b8d8
0x34b655…2a6f
4 touches
1 conflict
0x48ed1159…abe9
0x34ae4d…3fc5
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
21 conflicts on slot 0xe720a4c698…508eb0
Audit this contract →
← previous block·next block →recent activity