← previous blocknext block →recent activity
Analyzing
Block #106,916,104
39 transactions · 33 stateful · 2026-09-22 02:28:48 UTC
Parallelism
64/100
Blocked
61%
Avg conflicts / tx
1.82
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #106,916,104 · 39 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w310w011w112w213w314w415w516w617w718w819w920w1021w1122w1223w1337w238w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2130a548…c1de
0x34b655…2a6f
18 touches
36 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
16 touches
28 conflicts
0x49be85b3…1b66
0x34b655…2a6f
16 touches
28 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
14 touches
21 conflicts
0xe6a595bf…3c45
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 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
36 conflicts on slot 0x2130a548b9…31c1de
Audit this contract →
← previous block·next block →recent activity