Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b6e0a6703eeb813aa3de6d7ead1db9c908d918fa6998f5397d774052072113d

Tx prefix hash: 297ecb73510a82dcb7aeb1cf8f4a865a3eb2766fd04e03f6efef53ab4892fd2e
Tx public key: 26720f61096e191c8980b24b87443681dfefb5dd0c722d2303b7a7a17317d1f9
Timestamp: 1693297110 Timestamp [UCT]: 2023-08-29 08:18:30 Age [y:d:h:m:s]: 01:216:18:51:37
Block: 836350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416051 RingCT/type: yes/0
Extra: 0126720f61096e191c8980b24b87443681dfefb5dd0c722d2303b7a7a17317d1f902110000000275e3f0e9000000000000000000

1 output(s) for total of 1.039502029000 dcy

stealth address amount amount idx
00: 8b8545edc8c646aed807dc61850d90fc3e0f533140f1522bdc961a22d9e397f0 1.039502029000 1288934 of 0

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": 836360, "vin": [ { "gen": { "height": 836350 } } ], "vout": [ { "amount": 1039502029, "target": { "key": "8b8545edc8c646aed807dc61850d90fc3e0f533140f1522bdc961a22d9e397f0" } } ], "extra": [ 1, 38, 114, 15, 97, 9, 110, 25, 28, 137, 128, 178, 75, 135, 68, 54, 129, 223, 239, 181, 221, 12, 114, 45, 35, 3, 183, 167, 161, 115, 23, 209, 249, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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