Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39c60c4887e5f1cab9f9824e1d2386095e79d59ffa40640a6cb08ba5f5120e92

Tx prefix hash: d43630839bf9a6d4c9f4d0c586adc611719217cd3c5814818b3b73a624c672f9
Tx public key: 63fa78566c42c66bfff8c6e157ed6549bdae3ee1c0d967318696fe927091c10a
Timestamp: 1577377448 Timestamp [UCT]: 2019-12-26 16:24:08 Age [y:d:h:m:s]: 05:011:10:14:42
Block: 32311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1158137 RingCT/type: yes/0
Extra: 0163fa78566c42c66bfff8c6e157ed6549bdae3ee1c0d967318696fe927091c10a02110000021bc5b5978f000000000000000000

1 output(s) for total of 479.684953788000 dcy

stealth address amount amount idx
00: 26a17859bf8e4cbe15842ff1781e4a237fc15ee64f48efd84f21539d194af24d 479.684953788000 53714 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": 32321, "vin": [ { "gen": { "height": 32311 } } ], "vout": [ { "amount": 479684953788, "target": { "key": "26a17859bf8e4cbe15842ff1781e4a237fc15ee64f48efd84f21539d194af24d" } } ], "extra": [ 1, 99, 250, 120, 86, 108, 66, 198, 107, 255, 248, 198, 225, 87, 237, 101, 73, 189, 174, 62, 225, 192, 217, 103, 49, 134, 150, 254, 146, 112, 145, 193, 10, 2, 17, 0, 0, 2, 27, 197, 181, 151, 143, 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