← previous blocknext block →recent activity
Analyzing
Block #106,413,130
18 transactions · 18 stateful · 2026-09-20 08:16:15 UTC
Parallelism
61/100
Blocked
61%
Avg conflicts / tx
1.61
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,413,130 · 18 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
1w02w13w24w35w06w17w28w39w410w511w613w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fabbec…eaff
0x34b655…2a6f
14 touches
21 conflicts
0xfdd131fa…dbdb
0x34b655…2a6f
14 touches
21 conflicts
0x3fa1fac4…826c
0x34b655…2a6f
10 touches
10 conflicts
0x74e46435…fdcd
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0x4e7eb462…b2ad
0x1b6862…e19c
8 touches
6 conflicts
0xa1524d24…57bc
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
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
21 conflicts on slot 0xb3fabbec3b…a1eaff
Audit this contract →
← previous block·next block →recent activity