Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b0b7db5574200f8ec4d7463c31b2738f7284d7c305213cf750ec2063cdf1268

Tx prefix hash: 13ffa8534855e5f91e8f0a1fc7164e18073eaf2cb962c4cb2d00b6474490d9d7
Tx public key: 3fdca9fd7931d3bed8c89a67ad3910bd4789ceb4823c96b362f848ff8739a55c
Timestamp: 1704549180 Timestamp [UCT]: 2024-01-06 13:53:00 Age [y:d:h:m:s]: 01:310:19:22:13
Block: 929433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480977 RingCT/type: yes/0
Extra: 013fdca9fd7931d3bed8c89a67ad3910bd4789ceb4823c96b362f848ff8739a55c02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fc947e841eb5b5901dfd9f4ba0e8f33179efa3470af7d745e3f111b99e630b5 0.600000000000 1387305 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": 929443, "vin": [ { "gen": { "height": 929433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fc947e841eb5b5901dfd9f4ba0e8f33179efa3470af7d745e3f111b99e630b5" } } ], "extra": [ 1, 63, 220, 169, 253, 121, 49, 211, 190, 216, 200, 154, 103, 173, 57, 16, 189, 71, 137, 206, 180, 130, 60, 150, 179, 98, 248, 72, 255, 135, 57, 165, 92, 2, 17, 0, 0, 0, 5, 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