Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39d19fa23b5633acc9f29a2e0df8f7ceb4ec7fb32276823a6a359b36e8d0f1da

Tx prefix hash: f0ae55501520e6a6329256182b5c5e44e3ae87c4918b2d740c13f277dc9aea41
Tx public key: 64d846cea8e8775b608ef52247a8fdf27d0723fad82107eee1bd2196825c402e
Timestamp: 1639587283 Timestamp [UCT]: 2021-12-15 16:54:43 Age [y:d:h:m:s]: 03:054:06:14:37
Block: 396167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 817517 RingCT/type: yes/0
Extra: 0164d846cea8e8775b608ef52247a8fdf27d0723fad82107eee1bd2196825c402e02110000000dde12510f000000000000000000

1 output(s) for total of 29.876837798000 dcy

stealth address amount amount idx
00: 8108fc9180d63bc01bb5a7f1573403475a6010bc69e7b5622e2cf0115768fb89 29.876837798000 794344 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": 396177, "vin": [ { "gen": { "height": 396167 } } ], "vout": [ { "amount": 29876837798, "target": { "key": "8108fc9180d63bc01bb5a7f1573403475a6010bc69e7b5622e2cf0115768fb89" } } ], "extra": [ 1, 100, 216, 70, 206, 168, 232, 119, 91, 96, 142, 245, 34, 71, 168, 253, 242, 125, 7, 35, 250, 216, 33, 7, 238, 225, 189, 33, 150, 130, 92, 64, 46, 2, 17, 0, 0, 0, 13, 222, 18, 81, 15, 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