← previous blocknext block →recent activity
Analyzing
Block #104,333,444
26 transactions · 22 stateful · 2026-09-13 01:28:28 UTC
Parallelism
73/100
Blocked
32%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,333,444 · 26 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
1w02w16w28w315w418w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x9b44dbae…6602
0x34b655…2a6f
10 touches
10 conflicts
0x45de70d9…e1dc
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0xf61165ef…adb9
0x34b655…2a6f
4 touches
1 conflict
0xaf30c163…0fb6
0x34b655…2a6f
4 touches
1 conflict
0x5666db7d…5dc4
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