Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66cda9cedcf75c5273688b4cb6fb4bdffe8b9fd425410307e7f47bf31fc77f10

Tx prefix hash: 4fb10f664ba7e75b8a67c8cdd25f65d87cbffdd902a41d3c770c72c43853c090
Tx public key: 13257a06bdb193268f1152d63d31806a964ae9cded0a8cd986e5ced87f617221
Timestamp: 1713278955 Timestamp [UCT]: 2024-04-16 14:49:15 Age [y:d:h:m:s]: 01:027:19:05:25
Block: 1001817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280846 RingCT/type: yes/0
Extra: 0113257a06bdb193268f1152d63d31806a964ae9cded0a8cd986e5ced87f61722102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 578c29a51a0b9d7b4c8519e048d61dcdc5cfdd7fd6d2c38edb1e668122b3686c 0.600000000000 1462329 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": 1001827, "vin": [ { "gen": { "height": 1001817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "578c29a51a0b9d7b4c8519e048d61dcdc5cfdd7fd6d2c38edb1e668122b3686c" } } ], "extra": [ 1, 19, 37, 122, 6, 189, 177, 147, 38, 143, 17, 82, 214, 61, 49, 128, 106, 150, 74, 233, 205, 237, 10, 140, 217, 134, 229, 206, 216, 127, 97, 114, 33, 2, 17, 0, 0, 0, 1, 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