Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fe4c85ae9dc1434bd4929b7c9c1af8f8c3e2035a512484668661dc740777b65

Tx prefix hash: 434b720977c52e6087577c50099eed81612f8ba776806e35c46f6fbcc294e261
Tx public key: 9b80d5a9a7a602e72cbb598fbd8e03cd602118cad43c611a2d50e220bee38425
Timestamp: 1718489384 Timestamp [UCT]: 2024-06-15 22:09:44 Age [y:d:h:m:s]: 00:281:10:23:46
Block: 1045051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201088 RingCT/type: yes/0
Extra: 019b80d5a9a7a602e72cbb598fbd8e03cd602118cad43c611a2d50e220bee384250211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d08adc694489440c5141c89e6851fef7e414db4c3abebcc9dcb035d5db3c477 0.600000000000 1514520 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": 1045061, "vin": [ { "gen": { "height": 1045051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d08adc694489440c5141c89e6851fef7e414db4c3abebcc9dcb035d5db3c477" } } ], "extra": [ 1, 155, 128, 213, 169, 167, 166, 2, 231, 44, 187, 89, 143, 189, 142, 3, 205, 96, 33, 24, 202, 212, 60, 97, 26, 45, 80, 226, 32, 190, 227, 132, 37, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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