Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1664624370cc4d90c9c28e219e343b61e084185182bfad1b024663784e3ecbca

Tx prefix hash: b9937016e6c7f326ccf9e66e2a2f67acda1d100128ce4a3072ca0cb58f6bd3c1
Tx public key: 5a33d2c09ba63988072c72813e47a84a96c8c11d5466abca057cd76d4221b056
Timestamp: 1709292054 Timestamp [UCT]: 2024-03-01 11:20:54 Age [y:d:h:m:s]: 01:076:09:12:16
Block: 968789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315618 RingCT/type: yes/0
Extra: 015a33d2c09ba63988072c72813e47a84a96c8c11d5466abca057cd76d4221b05602110000000249a185bb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f92feb9e14bd7c08ac661801f6c09690f97ccbdd6ef65bbf370a03adf5be5ef 0.600000000000 1428612 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": 968799, "vin": [ { "gen": { "height": 968789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f92feb9e14bd7c08ac661801f6c09690f97ccbdd6ef65bbf370a03adf5be5ef" } } ], "extra": [ 1, 90, 51, 210, 192, 155, 166, 57, 136, 7, 44, 114, 129, 62, 71, 168, 74, 150, 200, 193, 29, 84, 102, 171, 202, 5, 124, 215, 109, 66, 33, 176, 86, 2, 17, 0, 0, 0, 2, 73, 161, 133, 187, 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