← previous blocknext block →recent activity
Analyzing
Block #104,196,177
13 transactions · 13 stateful · 2026-09-12 13:52:01 UTC
Parallelism
46/100
Blocked
46%
Avg conflicts / tx
1.62
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,196,177 · 13 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w28w310w411w512w6
- 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
12 touches
15 conflicts
0xf3736a38…a3af
0x34b655…2a6f
8 touches
6 conflicts
0xe1e5bf59…16a7
0x34b655…2a6f
6 touches
3 conflicts
0x6a0fc5e9…4571
0x34b655…2a6f
6 touches
3 conflicts
0xa47b7766…ee6e
0x34b655…2a6f
6 touches
3 conflicts
0xab981df1…2941
0x34b655…2a6f
4 touches
1 conflict
0xfe65bb7b…12d7
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity