Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9cc84e41962eec0e8efa4d67fcefc2069c09bd25d25b621676f7daeaff76344

Tx prefix hash: 340064e21ccb361ef3be2682326b5cd3eda655e6c36d68cd844d8202a80a833b
Tx public key: e164064fb520060c12918a7db68f9c7e5d9e13b432716807b7e9f0c9e34a3c32
Timestamp: 1759209460 Timestamp [UCT]: 2025-09-30 05:17:40 Age [y:d:h:m:s]: 00:045:03:34:46
Block: 1379487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32353 RingCT/type: yes/0
Extra: 01e164064fb520060c12918a7db68f9c7e5d9e13b432716807b7e9f0c9e34a3c3202110000000197baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59c32a529fdc04b81b17ba604c2a5aba1cf9f0b49998a70a60745057984a1b10 0.600000000000 1867584 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": 1379497, "vin": [ { "gen": { "height": 1379487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59c32a529fdc04b81b17ba604c2a5aba1cf9f0b49998a70a60745057984a1b10" } } ], "extra": [ 1, 225, 100, 6, 79, 181, 32, 6, 12, 18, 145, 138, 125, 182, 143, 156, 126, 93, 158, 19, 180, 50, 113, 104, 7, 183, 233, 240, 201, 227, 74, 60, 50, 2, 17, 0, 0, 0, 1, 151, 186, 249, 34, 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