Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a549875c769b9354bbce10c9675488f596ff9df250dbc1b6081ffd04c93008ae

Tx prefix hash: ecd8c03b30a7a011137cc7b0febf1d8099ef59a3fe0d58793ddc929ef308fe1b
Tx public key: 87f747f2589492c8d7d39004fcfd28da562b302f45e64f875a28c8a1f2f16af4
Timestamp: 1581518110 Timestamp [UCT]: 2020-02-12 14:35:10 Age [y:d:h:m:s]: 05:030:06:17:55
Block: 63633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1174306 RingCT/type: yes/0
Extra: 0187f747f2589492c8d7d39004fcfd28da562b302f45e64f875a28c8a1f2f16af402110000000312c4732d000000000000000000

1 output(s) for total of 377.709813552000 dcy

stealth address amount amount idx
00: 9e7ecf446927239f6fee504a8c87e035518c48bc3a0dfaf9b613dfe3fd04cc52 377.709813552000 117246 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": 63643, "vin": [ { "gen": { "height": 63633 } } ], "vout": [ { "amount": 377709813552, "target": { "key": "9e7ecf446927239f6fee504a8c87e035518c48bc3a0dfaf9b613dfe3fd04cc52" } } ], "extra": [ 1, 135, 247, 71, 242, 88, 148, 146, 200, 215, 211, 144, 4, 252, 253, 40, 218, 86, 43, 48, 47, 69, 230, 79, 135, 90, 40, 200, 161, 242, 241, 106, 244, 2, 17, 0, 0, 0, 3, 18, 196, 115, 45, 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