← previous blocknext block →recent activity
Analyzing
Block #106,935,463
51 transactions · 43 stateful · 2026-09-22 04:06:14 UTC
Parallelism
71/100
Blocked
65%
Avg conflicts / tx
1.53
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,935,463 · 51 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w17w28w39w410w119w422w223w328w630w231w136w339w240w441w743w145w947w1149w1350w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xc8c615d4…5da3
0x34b655…2a6f
12 touches
15 conflicts
0xc44fc151…bd06
0x34b655…2a6f
12 touches
15 conflicts
0xf7b76d2f…1b9c
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xb50ef533…79e4
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity