Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 559903370b59028d1f6b0d38f1a65cbf6ebd02256698d590b20fd35f718f3631

Tx prefix hash: 6929dd9f88cf79e7e947993b81eb7c4c5ca7d16c7b600e70e010eb49e358c943
Tx public key: 86faab0c39e8026bd26cedcb5fc0775b36ea75dcc5d805c4597831c6f3b7ec89
Timestamp: 1577765345 Timestamp [UCT]: 2019-12-31 04:09:05 Age [y:d:h:m:s]: 05:071:09:51:28
Block: 35457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1200851 RingCT/type: yes/0
Extra: 0186faab0c39e8026bd26cedcb5fc0775b36ea75dcc5d805c4597831c6f3b7ec8902110000003178873133000000000000000000

1 output(s) for total of 468.326883601000 dcy

stealth address amount amount idx
00: 96151fa7060cb637612f1e4de8ad574295d7dc236d5ace768072e3b855c615e2 468.326883601000 59808 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": 35467, "vin": [ { "gen": { "height": 35457 } } ], "vout": [ { "amount": 468326883601, "target": { "key": "96151fa7060cb637612f1e4de8ad574295d7dc236d5ace768072e3b855c615e2" } } ], "extra": [ 1, 134, 250, 171, 12, 57, 232, 2, 107, 210, 108, 237, 203, 95, 192, 119, 91, 54, 234, 117, 220, 197, 216, 5, 196, 89, 120, 49, 198, 243, 183, 236, 137, 2, 17, 0, 0, 0, 49, 120, 135, 49, 51, 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