Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b16de1ff0c1557b0b6550e9c11f17fff67a46349c67ff056080a1e6d8ee7b45

Tx prefix hash: c7885e3c6adf542038324e1bf6d64cf6e86a08fdf9e667183c35586f3be97812
Tx public key: 70f5f52ee55228ba3ca0ec6d40cd216fe6e11b0cb88a02d825f9f4a7d3cccf5f
Timestamp: 1706465326 Timestamp [UCT]: 2024-01-28 18:08:46 Age [y:d:h:m:s]: 01:072:07:34:12
Block: 945327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312767 RingCT/type: yes/0
Extra: 0170f5f52ee55228ba3ca0ec6d40cd216fe6e11b0cb88a02d825f9f4a7d3cccf5f02110000000181d71d55000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 541cc5c4de99c3532a8ffb511a5e881eabc86daaf36294b6e5e86257da585d06 0.600000000000 1403639 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": 945337, "vin": [ { "gen": { "height": 945327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "541cc5c4de99c3532a8ffb511a5e881eabc86daaf36294b6e5e86257da585d06" } } ], "extra": [ 1, 112, 245, 245, 46, 229, 82, 40, 186, 60, 160, 236, 109, 64, 205, 33, 111, 230, 225, 27, 12, 184, 138, 2, 216, 37, 249, 244, 167, 211, 204, 207, 95, 2, 17, 0, 0, 0, 1, 129, 215, 29, 85, 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