← previous blocknext block →recent activity
Analyzing
Block #104,333,082
20 transactions · 19 stateful · 2026-09-13 01:26:37 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,333,082 · 20 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
2w04w05w16w27w38w410w011w113w414w517w618w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x705a9a1a…db08
0x34b655…2a6f
14 touches
21 conflicts
0xec61dc1f…095f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x5666db7d…5dc4
0x34b655…2a6f
10 touches
10 conflicts
0x7b67f6cf…0aab
0x34b655…2a6f
8 touches
6 conflicts
0x02698894…0e5a
0x34b655…2a6f
6 touches
3 conflicts
0x23a320fb…cbd7
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
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
21 conflicts on slot 0x705a9a1af8…69db08
Audit this contract →
← previous block·next block →recent activity