Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 849c097701874c1a7e9915319c130cdf6b1fc67ca24f702dd992094dcd016f08

Tx prefix hash: 4ab8b3234b1af9414e4fec6e4071dae396b7a38ccc9e9e85632b87be935547ef
Tx public key: b3fdc30b3f3fc846111fe1bd189cd803e427b43bf75d68b7ac83d11eb7ccc3b9
Timestamp: 1736826999 Timestamp [UCT]: 2025-01-14 03:56:39 Age [y:d:h:m:s]: 00:154:08:43:03
Block: 1196917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110043 RingCT/type: yes/0
Extra: 01b3fdc30b3f3fc846111fe1bd189cd803e427b43bf75d68b7ac83d11eb7ccc3b90211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4975de86a2c9723d1d2813840d55e01a0220159f179ea7dc0a8ddaaac5f50768 0.600000000000 1683522 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": 1196927, "vin": [ { "gen": { "height": 1196917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4975de86a2c9723d1d2813840d55e01a0220159f179ea7dc0a8ddaaac5f50768" } } ], "extra": [ 1, 179, 253, 195, 11, 63, 63, 200, 70, 17, 31, 225, 189, 24, 156, 216, 3, 228, 39, 180, 59, 247, 93, 104, 183, 172, 131, 209, 30, 183, 204, 195, 185, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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