Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9341165c542a8a0c0f298ee0251e4e46100e3a8a76edbe106f146d751833437

Tx prefix hash: 55979ad4ea6005139d3257016fa812d384941077e9a0d6e69f76a6f13b2e6e9f
Tx public key: 192915536bfb56afdc66eabc2c882bc5d993e0a1c3a630263433a4a4b64fa847
Timestamp: 1710886765 Timestamp [UCT]: 2024-03-19 22:19:25 Age [y:d:h:m:s]: 01:232:01:58:10
Block: 982022 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424535 RingCT/type: yes/0
Extra: 01192915536bfb56afdc66eabc2c882bc5d993e0a1c3a630263433a4a4b64fa84702110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fa5ac491e9e164ee4c3eb5e865ea50ed6e2c127ca172ee4a119e6af2c25a202 0.600000000000 1442125 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": 982032, "vin": [ { "gen": { "height": 982022 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fa5ac491e9e164ee4c3eb5e865ea50ed6e2c127ca172ee4a119e6af2c25a202" } } ], "extra": [ 1, 25, 41, 21, 83, 107, 251, 86, 175, 220, 102, 234, 188, 44, 136, 43, 197, 217, 147, 224, 161, 195, 166, 48, 38, 52, 51, 164, 164, 182, 79, 168, 71, 2, 17, 0, 0, 0, 2, 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