Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c456cc411c5b39a6af0383cdb6c40fd8fc3c64ebc4f26b69c509ad02d8f7eaf

Tx prefix hash: 3bcc6716697a34fb3e1138e7f70db4a78c956f2c9eb5da5ad2a916c52dd4b05d
Tx public key: 4bba2be5b169ecb1ab2bf3b45a762e2a297ef6fa0f4a14cbe7d878fdbfdbff29
Timestamp: 1720408534 Timestamp [UCT]: 2024-07-08 03:15:34 Age [y:d:h:m:s]: 00:273:00:09:22
Block: 1060943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195043 RingCT/type: yes/0
Extra: 014bba2be5b169ecb1ab2bf3b45a762e2a297ef6fa0f4a14cbe7d878fdbfdbff29021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f8392f726c6945cefdaac4e24fa18852a6e8d8cf6a1fdbbf5961fc99c3c39ed 0.600000000000 1531432 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": 1060953, "vin": [ { "gen": { "height": 1060943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f8392f726c6945cefdaac4e24fa18852a6e8d8cf6a1fdbbf5961fc99c3c39ed" } } ], "extra": [ 1, 75, 186, 43, 229, 177, 105, 236, 177, 171, 43, 243, 180, 90, 118, 46, 42, 41, 126, 246, 250, 15, 74, 20, 203, 231, 216, 120, 253, 191, 219, 255, 41, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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