← previous blocknext block →recent activity
Analyzing
Block #106,931,733
19 transactions · 18 stateful · 2026-09-22 03:47:27 UTC
Parallelism
68/100
Blocked
61%
Avg conflicts / tx
1.26
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,931,733 · 19 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
1w02w13w26w07w18w29w310w211w112w413w514w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1b40f29…9b9d
0x34b655…2a6f
10 touches
10 conflicts
0x04994ed2…9032
0x34b655…2a6f
8 touches
6 conflicts
0x08385adf…0ed3
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x743f0e02…73ec
0x34b655…2a6f
8 touches
6 conflicts
0x10c19272…7444
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
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
10 conflicts on slot 0xd1b40f2924…ae9b9d
Audit this contract →
← previous block·next block →recent activity