Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddfb14dd7a5c2d1fc3b4e2c71bf872387212dc26940618201fcc8be7c2ccc112

Tx prefix hash: 17a1434d7dfbaaead673a522798d2cea1db1c9b41db1acc09618796ee7af8991
Tx public key: 7dde2e0c0d260a8c3cd1648bff030daf245fc31953d8662971919678db621ec7
Timestamp: 1745055818 Timestamp [UTC]: 2025-04-19 09:43:38 Age [y:d:h:m:s]: 01:210:16:54:55
Block: 1264767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414570 RingCT/type: yes/0
Extra: 017dde2e0c0d260a8c3cd1648bff030daf245fc31953d8662971919678db621ec7021100000004dbb571c1000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1723d5e4c4164b2e64cb71be318d4b9da35c26220bdd8ecdf156007516c4db6e 0.000600000000 1751968 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": 1264777, "vin": [ { "gen": { "height": 1264767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1723d5e4c4164b2e64cb71be318d4b9da35c26220bdd8ecdf156007516c4db6e" } } ], "extra": [ 1, 125, 222, 46, 12, 13, 38, 10, 140, 60, 209, 100, 139, 255, 3, 13, 175, 36, 95, 195, 25, 83, 216, 102, 41, 113, 145, 150, 120, 219, 98, 30, 199, 2, 17, 0, 0, 0, 4, 219, 181, 113, 193, 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: