Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69c67b2953ce1e340ef30834cc7b320cfb6d59affa8646f257954e190d1bddbb

Tx prefix hash: 70fdb3b18694cfb6e29f2ecfc68c9c27b3ee5201e51f6d261b38c2a1300a69a5
Tx public key: 085ddc9598c3aad79740e9666be5a0f9a6ae94ce9b78e6d836242f98acdcbbbd
Timestamp: 1762092989 Timestamp [UCT]: 2025-11-02 14:16:29 Age [y:d:h:m:s]: 00:017:16:36:10
Block: 1403398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12668 RingCT/type: yes/0
Extra: 01085ddc9598c3aad79740e9666be5a0f9a6ae94ce9b78e6d836242f98acdcbbbd021100000001df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31a7b57e988a6e9edbfa137480b0eaadcd0835fc8f2f18246abb64336b4b83d9 0.600000000000 1891739 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": 1403408, "vin": [ { "gen": { "height": 1403398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31a7b57e988a6e9edbfa137480b0eaadcd0835fc8f2f18246abb64336b4b83d9" } } ], "extra": [ 1, 8, 93, 220, 149, 152, 195, 170, 215, 151, 64, 233, 102, 107, 229, 160, 249, 166, 174, 148, 206, 155, 120, 230, 216, 54, 36, 47, 152, 172, 220, 187, 189, 2, 17, 0, 0, 0, 1, 223, 90, 36, 122, 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