Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 569c0a1ffde64aad13a9c60ef19e4cf38c134e61a94fdb658eec0024600669b0

Tx prefix hash: f1f9da29e15728a4a66e3bdd62cd1cc752133cea825ba1d41c4a39ea73911581
Tx public key: 5c1dfb94eb28817a6d298fb6a656b51655d3446cb0b9caeb08d3a8fd91050a42
Timestamp: 1705800581 Timestamp [UCT]: 2024-01-21 01:29:41 Age [y:d:h:m:s]: 01:083:10:20:15
Block: 939798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320751 RingCT/type: yes/0
Extra: 015c1dfb94eb28817a6d298fb6a656b51655d3446cb0b9caeb08d3a8fd91050a4202110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f667c897035b813b3869363763c7f88855cf6e4a95bba52cec62877ceae2173 0.600000000000 1397930 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": 939808, "vin": [ { "gen": { "height": 939798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f667c897035b813b3869363763c7f88855cf6e4a95bba52cec62877ceae2173" } } ], "extra": [ 1, 92, 29, 251, 148, 235, 40, 129, 122, 109, 41, 143, 182, 166, 86, 181, 22, 85, 211, 68, 108, 176, 185, 202, 235, 8, 211, 168, 253, 145, 5, 10, 66, 2, 17, 0, 0, 0, 11, 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