← previous blocknext block →recent activity
Analyzing
Block #101,937,204
55 transactions · 43 stateful · 2026-09-04 15:33:26 UTC
Parallelism
67/100
Blocked
60%
Avg conflicts / tx
1.69
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #101,937,204 · 55 txs across 18 waves · depth 18
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
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w16w08w19w212w213w314w015w117w418w519w620w723w224w831w233w348w1150w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x961a1ec2…c7b4
0xd32edf…ff58
11 touches
15 conflicts
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
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
45 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity