Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eef7afa94a75293a4b34cbed094ff479161e6c3456cf39cf7daec75931e15b75

Tx prefix hash: 8ed0858ffe62a6bf548c3c45848d2350f4983d2b7f3f389e79b3a06497d22469
Tx public key: 0a5a7024a57edf9e835b3af32cfb8189cdd822bb816fb6cdbf6a01705841dcb6
Timestamp: 1706557915 Timestamp [UCT]: 2024-01-29 19:51:55 Age [y:d:h:m:s]: 00:349:06:17:16
Block: 946094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250053 RingCT/type: yes/0
Extra: 010a5a7024a57edf9e835b3af32cfb8189cdd822bb816fb6cdbf6a01705841dcb602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1e45f64b464e2fba62508e1379e850c4c62c52b36addca9926b67830fb45e0f 0.600000000000 1404424 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": 946104, "vin": [ { "gen": { "height": 946094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1e45f64b464e2fba62508e1379e850c4c62c52b36addca9926b67830fb45e0f" } } ], "extra": [ 1, 10, 90, 112, 36, 165, 126, 223, 158, 131, 91, 58, 243, 44, 251, 129, 137, 205, 216, 34, 187, 129, 111, 182, 205, 191, 106, 1, 112, 88, 65, 220, 182, 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