Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a65ae3c6c4d6d18510fe325b2da4bbc33a2760fd12972d70976a68fe549a4d8

Tx prefix hash: dba54e905bc965d8244d98a4efa06694337399487b52612a3d826ace4b7f731d
Tx public key: 81515e9b50a83fa755011dc476550d50a6651304679208b4dae09c3a76a4f44f
Timestamp: 1700450883 Timestamp [UCT]: 2023-11-20 03:28:03 Age [y:d:h:m:s]: 01:122:20:09:04
Block: 895480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348964 RingCT/type: yes/0
Extra: 0181515e9b50a83fa755011dc476550d50a6651304679208b4dae09c3a76a4f44f021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.662068642000 dcy

stealth address amount amount idx
00: 0c7b057f83fc9386a2f7419def6806c7cf14ab3be2961177ea3ebb8815c7ec02 0.662068642000 1351717 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": 895490, "vin": [ { "gen": { "height": 895480 } } ], "vout": [ { "amount": 662068642, "target": { "key": "0c7b057f83fc9386a2f7419def6806c7cf14ab3be2961177ea3ebb8815c7ec02" } } ], "extra": [ 1, 129, 81, 94, 155, 80, 168, 63, 167, 85, 1, 29, 196, 118, 85, 13, 80, 166, 101, 19, 4, 103, 146, 8, 180, 218, 224, 156, 58, 118, 164, 244, 79, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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