Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d1b1dea1e032023b4ff724cfdcbd814f1095e08569067af710d6c1e2c8c0500

Tx prefix hash: 7e598dd6975b871ca76ee01faf417d569cce25038af56b9755936c079085efe2
Tx public key: 9cb750861ee8bbf373621a2609d8168251b6460020bd30a9eacf1a3f41e086ac
Timestamp: 1703158176 Timestamp [UCT]: 2023-12-21 11:29:36 Age [y:d:h:m:s]: 01:145:00:15:36
Block: 917927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364792 RingCT/type: yes/0
Extra: 019cb750861ee8bbf373621a2609d8168251b6460020bd30a9eacf1a3f41e086ac0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d73f816c2d0668b0d75174c9789479bf359c3eae8354d13ae9a8963a8f19ef20 0.600000000000 1375551 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": 917937, "vin": [ { "gen": { "height": 917927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d73f816c2d0668b0d75174c9789479bf359c3eae8354d13ae9a8963a8f19ef20" } } ], "extra": [ 1, 156, 183, 80, 134, 30, 232, 187, 243, 115, 98, 26, 38, 9, 216, 22, 130, 81, 182, 70, 0, 32, 189, 48, 169, 234, 207, 26, 63, 65, 224, 134, 172, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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