← previous blocknext block →recent activity
Analyzing
Block #106,009,646
25 transactions · 21 stateful · 2026-09-18 22:25:37 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
1.04
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,009,646 · 25 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
1w02w03w15w07w19w211w317w118w020w422w023w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
12 touches
15 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
12 touches
15 conflicts
0xd539bd36…9401
0x34b655…2a6f
10 touches
10 conflicts
0xfa5fc0e5…ff18
0x34b655…2a6f
10 touches
10 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
10 touches
10 conflicts
0x6940ae48…0c29
0x34b655…2a6f
8 touches
6 conflicts
0x7006165a…df17
0x34b655…2a6f
8 touches
6 conflicts
0xc32c7104…6608
0x34b655…2a6f
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
15 conflicts on slot 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity