Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9da7dfcf1c577cdde05ccfaedf5a615a48a10fc4fa99c3891500867193efcb01

Tx prefix hash: aa7ea59bc8737f67dba71c20b1da3f0d6cf2092f5af2038f0fad74077b04a356
Tx public key: dae4b66a0f9615a64ddedd317a9e13a56f9b5be8213353da93e120907b0dc0b9
Timestamp: 1742683971 Timestamp [UCT]: 2025-03-22 22:52:51 Age [y:d:h:m:s]: 00:310:04:05:02
Block: 1245150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219314 RingCT/type: yes/0
Extra: 01dae4b66a0f9615a64ddedd317a9e13a56f9b5be8213353da93e120907b0dc0b9021100000014af845649000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 277f4fc50726aea982c7d1470bdd58d95667c3a1c9203558de9d31552cdebc33 0.600000000000 1732141 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 dinasty-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": 1245160, "vin": [ { "gen": { "height": 1245150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "277f4fc50726aea982c7d1470bdd58d95667c3a1c9203558de9d31552cdebc33" } } ], "extra": [ 1, 218, 228, 182, 106, 15, 150, 21, 166, 77, 222, 221, 49, 122, 158, 19, 165, 111, 155, 91, 232, 33, 51, 83, 218, 147, 225, 32, 144, 123, 13, 192, 185, 2, 17, 0, 0, 0, 20, 175, 132, 86, 73, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8