Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c79e2cf0f58c21129a5cbec6f7ada91935c96f58aef8f38419e373092caf6a14

Tx prefix hash: 8698397d24dddcacabc69155d5a349e48645ac4b6465739b70dd856fc6789a42
Tx public key: 573cd8f4c258405c571d51adcacc40f214cb25b85cf42d5a8926b1cf969a7bb8
Timestamp: 1702457075 Timestamp [UCT]: 2023-12-13 08:44:35 Age [y:d:h:m:s]: 01:039:08:09:06
Block: 912137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289403 RingCT/type: yes/0
Extra: 01573cd8f4c258405c571d51adcacc40f214cb25b85cf42d5a8926b1cf969a7bb802110000000bfaf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7af87d1ea9309d0264affdbcef313a8303f6a7eec3be03df402cb301839e0e1 0.600000000000 1369357 of 15

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": 912147, "vin": [ { "gen": { "height": 912137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7af87d1ea9309d0264affdbcef313a8303f6a7eec3be03df402cb301839e0e1" } } ], "extra": [ 1, 87, 60, 216, 244, 194, 88, 64, 92, 87, 29, 81, 173, 202, 204, 64, 242, 20, 203, 37, 184, 92, 244, 45, 90, 137, 38, 177, 207, 150, 154, 123, 184, 2, 17, 0, 0, 0, 11, 250, 243, 92, 156, 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