← previous blocknext block →recent activity
Analyzing
Block #106,428,298
19 transactions · 18 stateful · 2026-09-20 09:32:35 UTC
Parallelism
63/100
Blocked
39%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,428,298 · 19 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
1w02w03w14w011w112w213w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d664414…3344
0x34b655…2a6f
12 touches
15 conflicts
0x856fe446…d9dd
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x172b0de5…980b
0x34b655…2a6f
8 touches
6 conflicts
0x065a3bb1…e176
0x34b655…2a6f
6 touches
3 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
6 touches
3 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
6 touches
3 conflicts
0xf6deafb5…5c25
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
15 conflicts on slot 0x8d664414de…103344
Audit this contract →
← previous block·next block →recent activity