← previous blocknext block →recent activity
Analyzing
Block #101,661,213
46 transactions · 36 stateful · 2026-09-03 16:23:15 UTC
Parallelism
70/100
Blocked
67%
Avg conflicts / tx
2.24
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #101,661,213 · 46 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
1w02w03w14w05w16w17w28w317w218w319w421w326w527w628w730w631w733w842w1143w1244w1345w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc6615a36…3cf0
0x34b655…2a6f
12 touches
15 conflicts
0x2139593e…16b8
0xd32edf…ff58
9 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xb3fb9fb5…64db
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity