← previous blocknext block →recent activity
Analyzing
Block #104,196,305
20 transactions · 19 stateful · 2026-09-12 13:52:40 UTC
Parallelism
70/100
Blocked
42%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,196,305 · 20 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
2w03w15w09w211w312w413w415w116w217w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x705a9a1a…db08
0x34b655…2a6f
6 touches
3 conflicts
0x8a294ae1…965c
0x34b655…2a6f
6 touches
3 conflicts
0x6183ee9a…21b1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb839a1e8…22b3
0x34b655…2a6f
4 touches
1 conflict
0xb9b077a8…e029
0x34b655…2a6f
4 touches
1 conflict
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity