Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 632434af56c7ed9d06195c9bc49e98b4e16eb155a42ce90adcc2a908856209fc

Tx prefix hash: 532c1641401a83b432d3e3ebcb8363cb419e15e8ec7508e05acc5c92831c3b3a
Tx public key: 1ea0b7b0d5deca293de9132c9065967987d8b25133513a54edf6b0812ce68188
Timestamp: 1708959098 Timestamp [UCT]: 2024-02-26 14:51:38 Age [y:d:h:m:s]: 01:110:03:38:14
Block: 966025 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339684 RingCT/type: yes/0
Extra: 011ea0b7b0d5deca293de9132c9065967987d8b25133513a54edf6b0812ce6818802110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5a8369b55f23ea05f6d288a063d6159c94cc276a4db11b628296283c3ee8701 0.600000000000 1425782 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": 966035, "vin": [ { "gen": { "height": 966025 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5a8369b55f23ea05f6d288a063d6159c94cc276a4db11b628296283c3ee8701" } } ], "extra": [ 1, 30, 160, 183, 176, 213, 222, 202, 41, 61, 233, 19, 44, 144, 101, 150, 121, 135, 216, 178, 81, 51, 81, 58, 84, 237, 246, 176, 129, 44, 230, 129, 136, 2, 17, 0, 0, 0, 4, 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