Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd946c0e1805032da8b0f409361ff8fb680627b8bcf9d919f5cfa6fb94102939

Tx prefix hash: 3916d3f996eb50f8c62b97214087557271a65bf6329980297b4f32e5fb708b83
Tx public key: b52f26f5332c7d712dd98e01f51be5e8d01006b1586af5b7b765b620be5c7c22
Timestamp: 1697087331 Timestamp [UCT]: 2023-10-12 05:08:51 Age [y:d:h:m:s]: 01:165:04:57:56
Block: 867805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379093 RingCT/type: yes/0
Extra: 01b52f26f5332c7d712dd98e01f51be5e8d01006b1586af5b7b765b620be5c7c220211000000064b8f5122000000000000000000

1 output(s) for total of 0.817714733000 dcy

stealth address amount amount idx
00: 9819466afe3e0e613c5f1b06396a3a293bd1fd09d74c73de2b99eedc4e492fd3 0.817714733000 1322523 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": 867815, "vin": [ { "gen": { "height": 867805 } } ], "vout": [ { "amount": 817714733, "target": { "key": "9819466afe3e0e613c5f1b06396a3a293bd1fd09d74c73de2b99eedc4e492fd3" } } ], "extra": [ 1, 181, 47, 38, 245, 51, 44, 125, 113, 45, 217, 142, 1, 245, 27, 229, 232, 208, 16, 6, 177, 88, 106, 245, 183, 183, 101, 182, 32, 190, 92, 124, 34, 2, 17, 0, 0, 0, 6, 75, 143, 81, 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