Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f03550e6d07f8e94951f415450ec65feb52fd4992b048f127a61772d8440d7a

Tx prefix hash: 705751356613459c438047c49a197d7e081a5ba00c133bb03c12ae3643bae808
Tx public key: aa7856234de3db96f74ad8a89b39b5ff20d8f8839c35bda51cc2dfabba33f21a
Timestamp: 1754139117 Timestamp [UCT]: 2025-08-02 12:51:57 Age [y:d:h:m:s]: 00:063:06:26:51
Block: 1338739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44043 RingCT/type: yes/0
Extra: 01aa7856234de3db96f74ad8a89b39b5ff20d8f8839c35bda51cc2dfabba33f21a021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4456b9f7fd61c44d3f4f985161d5d2e7e33397a5b77b0e8b057112763d9d3e67 0.600000000000 1826548 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": 1338749, "vin": [ { "gen": { "height": 1338739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4456b9f7fd61c44d3f4f985161d5d2e7e33397a5b77b0e8b057112763d9d3e67" } } ], "extra": [ 1, 170, 120, 86, 35, 77, 227, 219, 150, 247, 74, 216, 168, 155, 57, 181, 255, 32, 216, 248, 131, 156, 53, 189, 165, 28, 194, 223, 171, 186, 51, 242, 26, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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