Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 652ecb1fb34182d4badc2a91507f1714ddcdb3b9300616f81037d9da4b44db2b

Tx prefix hash: 066c6796b5744d8cae98d612ffd15097de6565b7a46937027b671fe8dc8a747c
Tx public key: d28d3067a6d75c28f041793caa6d0a07fef5b038e871ef16ae9963659249e1e2
Timestamp: 1734213176 Timestamp [UCT]: 2024-12-14 21:52:56 Age [y:d:h:m:s]: 00:113:03:52:48
Block: 1175295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80641 RingCT/type: yes/0
Extra: 01d28d3067a6d75c28f041793caa6d0a07fef5b038e871ef16ae9963659249e1e2021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64472c9b30fbdba1cc6031c0b63010d8a2225744b9781aa026b1445741189ae1 0.600000000000 1661554 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": 1175305, "vin": [ { "gen": { "height": 1175295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64472c9b30fbdba1cc6031c0b63010d8a2225744b9781aa026b1445741189ae1" } } ], "extra": [ 1, 210, 141, 48, 103, 166, 215, 92, 40, 240, 65, 121, 60, 170, 109, 10, 7, 254, 245, 176, 56, 232, 113, 239, 22, 174, 153, 99, 101, 146, 73, 225, 226, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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