← previous blocknext block →recent activity
Analyzing
Block #104,333,443
18 transactions · 17 stateful · 2026-09-13 01:28:28 UTC
Parallelism
72/100
Blocked
24%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,333,443 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w07w110w211w316w017w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b44dbae…6602
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0x5e4c5aad…1425
0x34b655…2a6f
4 touches
1 conflict
0x843b596d…0b18
0x34b655…2a6f
4 touches
1 conflict
0x97420b44…a2a8
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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 0x9b44dbaece…506602
Audit this contract →
← previous block·next block →recent activity