Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b92451a953f461e0979ec38bbe2673eabc909af988ce00945db13d43e7b8813e

Tx prefix hash: f78cdd683a5ddfcba9d6f5b8a0e7c46abb2a507154fa00d9ee493663948563f5
Tx public key: ce5944570dab26e8a63059e47feb92eda73c4f1aa0d6a56cbf23251b075ec60c
Timestamp: 1639471996 Timestamp [UCT]: 2021-12-14 08:53:16 Age [y:d:h:m:s]: 03:153:08:15:17
Block: 395225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 888363 RingCT/type: yes/0
Extra: 01ce5944570dab26e8a63059e47feb92eda73c4f1aa0d6a56cbf23251b075ec60c02110000000175e655a0000000000000000000

1 output(s) for total of 30.092333601000 dcy

stealth address amount amount idx
00: d8aea6cdac2b064e0baa3c5845dc25bcd6efa3571ad33da44de3a765423d3694 30.092333601000 793072 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": 395235, "vin": [ { "gen": { "height": 395225 } } ], "vout": [ { "amount": 30092333601, "target": { "key": "d8aea6cdac2b064e0baa3c5845dc25bcd6efa3571ad33da44de3a765423d3694" } } ], "extra": [ 1, 206, 89, 68, 87, 13, 171, 38, 232, 166, 48, 89, 228, 127, 235, 146, 237, 167, 60, 79, 26, 160, 214, 165, 108, 191, 35, 37, 27, 7, 94, 198, 12, 2, 17, 0, 0, 0, 1, 117, 230, 85, 160, 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