← previous blocknext block →recent activity
Analyzing
Block #104,166,408
26 transactions · 24 stateful · 2026-09-12 11:21:02 UTC
Parallelism
62/100
Blocked
46%
Avg conflicts / tx
1.88
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #104,166,408 · 26 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w28w316w417w518w620w723w824w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0xd66696e0…0842
0x34b655…2a6f
12 touches
15 conflicts
0x5d6da397…6c5c
0x34b655…2a6f
12 touches
15 conflicts
0x64275949…d698
0x34b655…2a6f
10 touches
10 conflicts
0xe7b9eede…2538
0x34b655…2a6f
10 touches
10 conflicts
0xa3250389…8774
0x34b655…2a6f
10 touches
10 conflicts
0x0ddfdaf2…9e00
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity