← previous blocknext block →recent activity
Analyzing
Block #104,203,441
22 transactions · 17 stateful · 2026-09-12 14:28:57 UTC
Parallelism
73/100
Blocked
41%
Avg conflicts / tx
0.91
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,203,441 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w26w011w012w114w315w416w520w021w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6dedaff6…161b
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x09ad83be…79ff
0x34b655…2a6f
8 touches
6 conflicts
0xb9b077a8…e029
0x34b655…2a6f
6 touches
3 conflicts
0x70a7b5d6…fe0e
0x34b655…2a6f
6 touches
3 conflicts
0x4af57871…9f3f
0x34b655…2a6f
6 touches
3 conflicts
0xf2eb1f3c…ab07
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 0x6dedaff684…2d161b
Audit this contract →
← previous block·next block →recent activity