Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4fab7a0c7d0d54eda0586f47983d6c3734b9b0381b694dc046d50ea8e3b948e

Tx prefix hash: 3cf4045f7f455836ca777591583dec0e2821b145791c250b89c588f6ea636d15
Tx public key: 90f13390dc98ab1381a52da742519708f2901a1c56b1a506ff8f9fa79e6e4b26
Timestamp: 1708923113 Timestamp [UCT]: 2024-02-26 04:51:53 Age [y:d:h:m:s]: 01:253:01:52:16
Block: 965727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439594 RingCT/type: yes/0
Extra: 0190f13390dc98ab1381a52da742519708f2901a1c56b1a506ff8f9fa79e6e4b260211000000060546d7d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d6ebe010845357e50298300c8c36620464fc694a8c9b635c7c804e3d37027ff 0.600000000000 1425482 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": 965737, "vin": [ { "gen": { "height": 965727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d6ebe010845357e50298300c8c36620464fc694a8c9b635c7c804e3d37027ff" } } ], "extra": [ 1, 144, 241, 51, 144, 220, 152, 171, 19, 129, 165, 45, 167, 66, 81, 151, 8, 242, 144, 26, 28, 86, 177, 165, 6, 255, 143, 159, 167, 158, 110, 75, 38, 2, 17, 0, 0, 0, 6, 5, 70, 215, 208, 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