Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 085d6c0c20ace1b295d2eb7c18cd6b9b4cf8dd3acee85c966b73a7f124bdf7c2

Tx prefix hash: 69e3c28cf8b237b19c26897fd50a004e866d20d852571eec911a7292346ca4c6
Tx public key: b54ad0629a64228191d674280a681657e02d2cb6744804919619468049c7804d
Timestamp: 1734347243 Timestamp [UCT]: 2024-12-16 11:07:23 Age [y:d:h:m:s]: 00:117:14:56:24
Block: 1176409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83836 RingCT/type: yes/0
Extra: 01b54ad0629a64228191d674280a681657e02d2cb6744804919619468049c7804d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc2d2e1f2d71fad8d5a8a13b3077e97864ac015c008d260a79ac64de299a82d3 0.600000000000 1662742 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": 1176419, "vin": [ { "gen": { "height": 1176409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc2d2e1f2d71fad8d5a8a13b3077e97864ac015c008d260a79ac64de299a82d3" } } ], "extra": [ 1, 181, 74, 208, 98, 154, 100, 34, 129, 145, 214, 116, 40, 10, 104, 22, 87, 224, 45, 44, 182, 116, 72, 4, 145, 150, 25, 70, 128, 73, 199, 128, 77, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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