Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f63f67289c09f6dc87bdba726d2efd9cd5751b74b3e7c7ebaa2af54dcc39718a

Tx prefix hash: 3f73428a2e0b1c6a5e6496a04de21be2a415c10bff076b0c61624ebd1cf2848f
Tx public key: aaeff87fc4b0dd18905976c147f8df1d3267a410b108187932d4c13537c2d85b
Timestamp: 1775159908 Timestamp [UTC]: 2026-04-02 19:58:28 Age [y:d:h:m:s]: 00:225:16:18:59
Block: 1511443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166685 RingCT/type: yes/0
Extra: 01aaeff87fc4b0dd18905976c147f8df1d3267a410b108187932d4c13537c2d85b021100000001e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a969020254e02d1a85445e198577107e99b0e49067a2b07eb89454c63b9c203d 0.000600000000 2001235 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1511453, "vin": [ { "gen": { "height": 1511443 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a969020254e02d1a85445e198577107e99b0e49067a2b07eb89454c63b9c203d" } } ], "extra": [ 1, 170, 239, 248, 127, 196, 176, 221, 24, 144, 89, 118, 193, 71, 248, 223, 29, 50, 103, 164, 16, 177, 8, 24, 121, 50, 212, 193, 53, 55, 194, 216, 91, 2, 17, 0, 0, 0, 1, 227, 215, 220, 159, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: