Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6dc68f9d81ddbeda4c083085124df042e7d2b03c2c366bff84a674d94ce756d

Tx prefix hash: 2b98ac95e306667d5bb406e0493def921e52a537b47156d3d33d5e0208849d7b
Tx public key: da839f8553bcaa1a81c54595d7e804cd442f11e1d151f119159f01889e1abcca
Timestamp: 1706257578 Timestamp [UCT]: 2024-01-26 08:26:18 Age [y:d:h:m:s]: 01:034:07:42:21
Block: 943599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285592 RingCT/type: yes/0
Extra: 01da839f8553bcaa1a81c54595d7e804cd442f11e1d151f119159f01889e1abcca02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76f51c6a833a2f945861093c991b5c66e515bc877e2d593455b73dc1b954b8d0 0.600000000000 1401807 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": 943609, "vin": [ { "gen": { "height": 943599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76f51c6a833a2f945861093c991b5c66e515bc877e2d593455b73dc1b954b8d0" } } ], "extra": [ 1, 218, 131, 159, 133, 83, 188, 170, 26, 129, 197, 69, 149, 215, 232, 4, 205, 68, 47, 17, 225, 209, 81, 241, 25, 21, 159, 1, 136, 158, 26, 188, 202, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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