Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 539b5edbef69992ff966441d77eb92c0b89f00f60103dee1122f463410fcbbb0

Tx prefix hash: bf47a6714b297ce10ea20c007b37d7738a9e079ebb31c82a38336ab73633b5ed
Tx public key: 74fb563f1d5c4de6008df298b106d7b5a2ed4a16fd48409f73125afa9fa56396
Timestamp: 1634725511 Timestamp [UCT]: 2021-10-20 10:25:11 Age [y:d:h:m:s]: 03:019:08:23:56
Block: 356734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 791981 RingCT/type: yes/0
Extra: 0174fb563f1d5c4de6008df298b106d7b5a2ed4a16fd48409f73125afa9fa5639602110000000cf29d7abf000000000000000000

1 output(s) for total of 40.363850076000 dcy

stealth address amount amount idx
00: a4e086b156810a61c2367fe47f761ae04c3a4e31e1060544e8752dca2a8f89b5 40.363850076000 727728 of 0

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": 356744, "vin": [ { "gen": { "height": 356734 } } ], "vout": [ { "amount": 40363850076, "target": { "key": "a4e086b156810a61c2367fe47f761ae04c3a4e31e1060544e8752dca2a8f89b5" } } ], "extra": [ 1, 116, 251, 86, 63, 29, 92, 77, 230, 0, 141, 242, 152, 177, 6, 215, 181, 162, 237, 74, 22, 253, 72, 64, 159, 115, 18, 90, 250, 159, 165, 99, 150, 2, 17, 0, 0, 0, 12, 242, 157, 122, 191, 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