Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f34edfa40c93ad684b98f7019def5147393d94e3922ebe02868e384d5b1b0b19

Tx prefix hash: 856b84cd3d184a4cd762682a17e81d3549dd6635576a2c00f2b25d99e9be7d6f
Tx public key: 5cb417cc7fa65f6a3d54c62cf0d1fba2464efa493beb27d6d3f7c5de15bf5a3b
Timestamp: 1576266121 Timestamp [UCT]: 2019-12-13 19:42:01 Age [y:d:h:m:s]: 04:328:05:21:43
Block: 26412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1120331 RingCT/type: yes/0
Extra: 015cb417cc7fa65f6a3d54c62cf0d1fba2464efa493beb27d6d3f7c5de15bf5a3b0211000000024943cd9f000000000000000000

1 output(s) for total of 501.749498867000 dcy

stealth address amount amount idx
00: f4038e5a70c00d56d217eebc2b46f281161787219714e59de98c23ef08b230e2 501.749498867000 43741 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": 26422, "vin": [ { "gen": { "height": 26412 } } ], "vout": [ { "amount": 501749498867, "target": { "key": "f4038e5a70c00d56d217eebc2b46f281161787219714e59de98c23ef08b230e2" } } ], "extra": [ 1, 92, 180, 23, 204, 127, 166, 95, 106, 61, 84, 198, 44, 240, 209, 251, 162, 70, 78, 250, 73, 59, 235, 39, 214, 211, 247, 197, 222, 21, 191, 90, 59, 2, 17, 0, 0, 0, 2, 73, 67, 205, 159, 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