Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f3fffa8b225194aa467b8a41ddccd5c4dc71a997a5918719838b903bb4457e1

Tx prefix hash: 831734e6d8cc3805900a99d6719d0defca5902eab39722dc3126257955e3dcb8
Tx public key: 4790e6dab52c69d959797077b28cd9421cf1bf5139f4e3669e07614b676975f6
Timestamp: 1574459206 Timestamp [UCT]: 2019-11-22 21:46:46 Age [y:d:h:m:s]: 05:114:02:56:38
Block: 14782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1224702 RingCT/type: yes/0
Extra: 014790e6dab52c69d959797077b28cd9421cf1bf5139f4e3669e07614b676975f6021100000008f95225a5000000000000000000

1 output(s) for total of 548.304717116000 dcy

stealth address amount amount idx
00: de1fa3d48b9e8d3a98e661bcf43d9c301f41e169df1ce38ac97f37824caa685c 548.304717116000 19122 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": 14792, "vin": [ { "gen": { "height": 14782 } } ], "vout": [ { "amount": 548304717116, "target": { "key": "de1fa3d48b9e8d3a98e661bcf43d9c301f41e169df1ce38ac97f37824caa685c" } } ], "extra": [ 1, 71, 144, 230, 218, 181, 44, 105, 217, 89, 121, 112, 119, 178, 140, 217, 66, 28, 241, 191, 81, 57, 244, 227, 102, 158, 7, 97, 75, 103, 105, 117, 246, 2, 17, 0, 0, 0, 8, 249, 82, 37, 165, 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