Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d7431dfb6d95299e24caea76a9613f7d736a98ad16d81dcfb37d2a05809dc16

Tx prefix hash: b77087cd2465a5a52c4616a356f1b89247a397b4c3a9f6a3d6a3281b03e1d6dd
Tx public key: 247a08034713de35871248cfb629720fa39bd7bfefaa75566a42df954acf2923
Timestamp: 1707011446 Timestamp [UCT]: 2024-02-04 01:50:46 Age [y:d:h:m:s]: 01:065:14:55:22
Block: 949854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307971 RingCT/type: yes/0
Extra: 01247a08034713de35871248cfb629720fa39bd7bfefaa75566a42df954acf292302110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c41ed8a83150511f154e03a5a6ce6f5b85a7c49d16e9d70c0554a7d6c41cbba 0.600000000000 1408388 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": 949864, "vin": [ { "gen": { "height": 949854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c41ed8a83150511f154e03a5a6ce6f5b85a7c49d16e9d70c0554a7d6c41cbba" } } ], "extra": [ 1, 36, 122, 8, 3, 71, 19, 222, 53, 135, 18, 72, 207, 182, 41, 114, 15, 163, 155, 215, 191, 239, 170, 117, 86, 106, 66, 223, 149, 74, 207, 41, 35, 2, 17, 0, 0, 0, 9, 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