Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 089a4ac2488ecbb912ac79366f31898f0789a926d64ed9a4a2223e72797978da

Tx prefix hash: 854090dc61c9da6c3ac1ae4b015cf23b10aab0ef75878bfafeb166b39154bfea
Tx public key: 4df4a8591c8bd94a077b050902fb075ba052cddab37a2ebe427e3c5e84ffd842
Timestamp: 1729471442 Timestamp [UCT]: 2024-10-21 00:44:02 Age [y:d:h:m:s]: 00:143:10:20:13
Block: 1136047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102316 RingCT/type: yes/0
Extra: 014df4a8591c8bd94a077b050902fb075ba052cddab37a2ebe427e3c5e84ffd842021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25916e7558948f6fd215c99b1898499464e04363e3aa0c13e98cf3dcb6806c40 0.600000000000 1619390 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": 1136057, "vin": [ { "gen": { "height": 1136047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25916e7558948f6fd215c99b1898499464e04363e3aa0c13e98cf3dcb6806c40" } } ], "extra": [ 1, 77, 244, 168, 89, 28, 139, 217, 74, 7, 123, 5, 9, 2, 251, 7, 91, 160, 82, 205, 218, 179, 122, 46, 190, 66, 126, 60, 94, 132, 255, 216, 66, 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