← previous blocknext block →recent activity
Analyzing
Block #104,193,739
12 transactions · 11 stateful · 2026-09-12 13:39:33 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,193,739 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w18w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5c98027…9fd9
0x34b655…2a6f
6 touches
3 conflicts
0xa4e9800f…4ab0
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x0c78ade3…f11a
0x34b655…2a6f
5 touches
3 conflicts
0x8efdc9c2…f056
0x34b655…2a6f
5 touches
3 conflicts
0x67c69db9…7906
0x34b655…2a6f
4 touches
1 conflict
0xaceaf2ae…52e8
0x34b655…2a6f
4 touches
1 conflict
0xb6ed530c…d450
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
3 conflicts on slot 0xd5c98027d8…499fd9
Audit this contract →
← previous block·next block →recent activity