Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ac04d1d56c953b21eb16b4d8a607d36e0573c6d7c3c0accebbff63a55f20262

Tx prefix hash: 3074a7475efaf1e470115aa5fdabaf637a7e67d39fc13cc7e7161b5322b01917
Tx public key: 5f22945a396ae427c3cfd5ac6d8d30f566a1a21c77cc6b9b5857b6a0e2f5ffec
Timestamp: 1577711890 Timestamp [UCT]: 2019-12-30 13:18:10 Age [y:d:h:m:s]: 05:007:14:31:10
Block: 35048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1155432 RingCT/type: yes/0
Extra: 015f22945a396ae427c3cfd5ac6d8d30f566a1a21c77cc6b9b5857b6a0e2f5ffec0211000000098a2ee0d9000000000000000000

1 output(s) for total of 469.755941482000 dcy

stealth address amount amount idx
00: 17a52b55b6b46abc8bae7f2fce81903aff35d9a82a80460485967e133f4170c1 469.755941482000 59041 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": 35058, "vin": [ { "gen": { "height": 35048 } } ], "vout": [ { "amount": 469755941482, "target": { "key": "17a52b55b6b46abc8bae7f2fce81903aff35d9a82a80460485967e133f4170c1" } } ], "extra": [ 1, 95, 34, 148, 90, 57, 106, 228, 39, 195, 207, 213, 172, 109, 141, 48, 245, 102, 161, 162, 28, 119, 204, 107, 155, 88, 87, 182, 160, 226, 245, 255, 236, 2, 17, 0, 0, 0, 9, 138, 46, 224, 217, 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