Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba0dc05f85455054b5023a3745740c700a840f127e6afa50842921993a6c9553

Tx prefix hash: 1960390ba2f39a0d3fc26fbe10f263f437b3684a5dcd08d0c317b87aa8d2035f
Tx public key: df9b922172cb0d37a10d202a2cc5e35f9ab111ef15d1762cb3c28077c322759f
Timestamp: 1577961659 Timestamp [UCT]: 2020-01-02 10:40:59 Age [y:d:h:m:s]: 05:097:18:08:03
Block: 37156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1219587 RingCT/type: yes/0
Extra: 01df9b922172cb0d37a10d202a2cc5e35f9ab111ef15d1762cb3c28077c322759f02110000001c4943cd9f000000000000000000

1 output(s) for total of 462.261367377000 dcy

stealth address amount amount idx
00: 969fe7a78e1d556005e1e3fa3cea6dace04449137cf3bb91b03a39abdcb96071 462.261367377000 63004 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": 37166, "vin": [ { "gen": { "height": 37156 } } ], "vout": [ { "amount": 462261367377, "target": { "key": "969fe7a78e1d556005e1e3fa3cea6dace04449137cf3bb91b03a39abdcb96071" } } ], "extra": [ 1, 223, 155, 146, 33, 114, 203, 13, 55, 161, 13, 32, 42, 44, 197, 227, 95, 154, 177, 17, 239, 21, 209, 118, 44, 179, 194, 128, 119, 195, 34, 117, 159, 2, 17, 0, 0, 0, 28, 73, 67, 205, 159, 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