Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5656af47db4987f14482505e72e5eff52b0f802bfec70cf14fd69d6aad7ec090

Tx prefix hash: bbc6c56a16e279d028173089b0bfab8e78da98bad0197f9300be448ee932d3b2
Tx public key: cc684b49d49ff5ec2680f322b1a7c80d1a835120c785902b2f2ac9ecb03dd0b2
Timestamp: 1703428484 Timestamp [UCT]: 2023-12-24 14:34:44 Age [y:d:h:m:s]: 01:321:05:39:23
Block: 920175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488429 RingCT/type: yes/0
Extra: 01cc684b49d49ff5ec2680f322b1a7c80d1a835120c785902b2f2ac9ecb03dd0b202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de24c509c5e4a992ffb25ddc05f057663b016f4e710fa3c88fc5fb409711fdc4 0.600000000000 1377853 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": 920185, "vin": [ { "gen": { "height": 920175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de24c509c5e4a992ffb25ddc05f057663b016f4e710fa3c88fc5fb409711fdc4" } } ], "extra": [ 1, 204, 104, 75, 73, 212, 159, 245, 236, 38, 128, 243, 34, 177, 167, 200, 13, 26, 131, 81, 32, 199, 133, 144, 43, 47, 42, 201, 236, 176, 61, 208, 178, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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