Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd3f8c2fc6d781e7da576918c9f06b019275b53ab2396baf1ec1de2e8c73217c

Tx prefix hash: d235cb392cfbec11c0b4dda35bc3d4cd0ee2b542da1e0d9eabde0fc781c33242
Tx public key: 914b5450dd4ccc087bbeef24238d0f407a8248ea3df6e8499218f7df3adfb778
Timestamp: 1574714430 Timestamp [UCT]: 2019-11-25 20:40:30 Age [y:d:h:m:s]: 04:342:03:18:59
Block: 17405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126456 RingCT/type: yes/0
Extra: 01914b5450dd4ccc087bbeef24238d0f407a8248ea3df6e8499218f7df3adfb778021100000001f95225a5000000000000000000

1 output(s) for total of 537.441118671000 dcy

stealth address amount amount idx
00: ba52dd8beeaed66c697f9aafcef9517ac8c91d44e55dcf6986257ac8a7903c96 537.441118671000 25267 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": 17415, "vin": [ { "gen": { "height": 17405 } } ], "vout": [ { "amount": 537441118671, "target": { "key": "ba52dd8beeaed66c697f9aafcef9517ac8c91d44e55dcf6986257ac8a7903c96" } } ], "extra": [ 1, 145, 75, 84, 80, 221, 76, 204, 8, 123, 190, 239, 36, 35, 141, 15, 64, 122, 130, 72, 234, 61, 246, 232, 73, 146, 24, 247, 223, 58, 223, 183, 120, 2, 17, 0, 0, 0, 1, 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