← previous blocknext block →recent activity
Analyzing
Block #104,320,365
14 transactions · 13 stateful · 2026-09-13 00:22:05 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #104,320,365 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w19w010w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc38f208c…1dea
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xcea40325…6b39
0x34b655…2a6f
4 touches
1 conflict
0xd168ad41…3e19
0x34b655…2a6f
4 touches
1 conflict
0x152fb441…a688
0x34b655…2a6f
4 touches
1 conflict
0x2f0a05e2…5cbb
0x34b655…2a6f
4 touches
1 conflict
0x60f63d67…5ba0
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 0xc38f208c59…111dea
Audit this contract →
← previous block·next block →recent activity