Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0d91e180e155a48dc6dee1a6c91a7aed6ceba47bd07a5b612ff52016c5ec2c1

Tx prefix hash: dd4d679ebcf33d781361358b43f23f50ca5920b136c571a9b16c5c980a050d06
Tx public key: f56cae35ec4d527d58abf29101f69941b48ec918dd36fa4a468080449e7f0d1b
Timestamp: 1730660566 Timestamp [UCT]: 2024-11-03 19:02:46 Age [y:d:h:m:s]: 00:109:15:16:57
Block: 1145851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78148 RingCT/type: yes/0
Extra: 01f56cae35ec4d527d58abf29101f69941b48ec918dd36fa4a468080449e7f0d1b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bdaf0a388b31156f73a67ce69802f405425345c0178d5376c3f7d2d9b697f91 0.600000000000 1630376 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": 1145861, "vin": [ { "gen": { "height": 1145851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bdaf0a388b31156f73a67ce69802f405425345c0178d5376c3f7d2d9b697f91" } } ], "extra": [ 1, 245, 108, 174, 53, 236, 77, 82, 125, 88, 171, 242, 145, 1, 246, 153, 65, 180, 142, 201, 24, 221, 54, 250, 74, 70, 128, 128, 68, 158, 127, 13, 27, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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