Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bc4cf700fad9d105820a0b4731fe6526af667681beaa8f29e28a93ff900c708

Tx prefix hash: eac8ca0c75d10334ce4dc253e1514472a9d74f57d5ed6bc8cddec47798d81e4e
Tx public key: fe23ba7950bf68b63e0db4b945ce78bda92510af30814798c0b874c14f818d9f
Timestamp: 1696003019 Timestamp [UCT]: 2023-09-29 15:56:59 Age [y:d:h:m:s]: 01:048:03:40:52
Block: 858814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295638 RingCT/type: yes/0
Extra: 01fe23ba7950bf68b63e0db4b945ce78bda92510af30814798c0b874c14f818d9f02110000000875e3f0e9000000000000000000

1 output(s) for total of 0.875775418000 dcy

stealth address amount amount idx
00: ea589c36854535cd2dc5a08163ea475060b4f1559430bb62feffa5825e6c23e7 0.875775418000 1313010 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": 858824, "vin": [ { "gen": { "height": 858814 } } ], "vout": [ { "amount": 875775418, "target": { "key": "ea589c36854535cd2dc5a08163ea475060b4f1559430bb62feffa5825e6c23e7" } } ], "extra": [ 1, 254, 35, 186, 121, 80, 191, 104, 182, 62, 13, 180, 185, 69, 206, 120, 189, 169, 37, 16, 175, 48, 129, 71, 152, 192, 184, 116, 193, 79, 129, 141, 159, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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