Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b22a7ddcd54e7e33912e13522c0c4e6eadbf5fa96ea63296588101db6d3e46b5

Tx prefix hash: 8dd7ebce734f184d0f617065e598115824a2233448f0824c229dae6a8513220c
Tx public key: fff11f805b41e94edc0f1c9c26b82fabcfa50190cef43ce83ff7a6cf309e3607
Timestamp: 1745796096 Timestamp [UCT]: 2025-04-27 23:21:36 Age [y:d:h:m:s]: 00:207:04:41:57
Block: 1270906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145785 RingCT/type: yes/0
Extra: 01fff11f805b41e94edc0f1c9c26b82fabcfa50190cef43ce83ff7a6cf309e36070211000000049f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1a8e7db989c9c4d5f95938c5461c72a9cef9a17f9b06dfb1bc1ac482a9ed793 0.600000000000 1758151 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": 1270916, "vin": [ { "gen": { "height": 1270906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1a8e7db989c9c4d5f95938c5461c72a9cef9a17f9b06dfb1bc1ac482a9ed793" } } ], "extra": [ 1, 255, 241, 31, 128, 91, 65, 233, 78, 220, 15, 28, 156, 38, 184, 47, 171, 207, 165, 1, 144, 206, 244, 60, 232, 63, 247, 166, 207, 48, 158, 54, 7, 2, 17, 0, 0, 0, 4, 159, 159, 230, 140, 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