Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2449eaabe2615ec0b7cb9af572d974fab758165ec430c7b666307e673d3356a3

Tx prefix hash: 27391d8ed867665dc5823224bcb541ff6774b377f6aa25ca02cd20bec97433e9
Tx public key: c6e935352dd4bb2c1fc694689b2e85d040da7c15e38b9d24e2b481c76d40f205
Timestamp: 1578835385 Timestamp [UCT]: 2020-01-12 13:23:05 Age [y:d:h:m:s]: 05:293:12:00:34
Block: 43995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1357611 RingCT/type: yes/0
Extra: 01c6e935352dd4bb2c1fc694689b2e85d040da7c15e38b9d24e2b481c76d40f20502110000004bff58ae94000000000000000000

1 output(s) for total of 438.760116967000 dcy

stealth address amount amount idx
00: 2ed89051ec21159ce6044c0264ee1d4023302d31d3179cb87fc5fb3d88354533 438.760116967000 79897 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": 44005, "vin": [ { "gen": { "height": 43995 } } ], "vout": [ { "amount": 438760116967, "target": { "key": "2ed89051ec21159ce6044c0264ee1d4023302d31d3179cb87fc5fb3d88354533" } } ], "extra": [ 1, 198, 233, 53, 53, 45, 212, 187, 44, 31, 198, 148, 104, 155, 46, 133, 208, 64, 218, 124, 21, 227, 139, 157, 36, 226, 180, 129, 199, 109, 64, 242, 5, 2, 17, 0, 0, 0, 75, 255, 88, 174, 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