Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8c11643388a20a45453aeec31d51738ca5cad15071c5dc309a7ae1310bb5d14

Tx prefix hash: 16ad5f3347fa484e5f4f78c7ec0737cde00d27afc2443cc585914578f0ef3dca
Tx public key: 650f7f29514b6f3ef848c8bba47fb41b280133aefdf0278c45031c6e5490bd2d
Timestamp: 1717988893 Timestamp [UCT]: 2024-06-10 03:08:13 Age [y:d:h:m:s]: 00:340:14:22:13
Block: 1040884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243430 RingCT/type: yes/0
Extra: 01650f7f29514b6f3ef848c8bba47fb41b280133aefdf0278c45031c6e5490bd2d0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5209b96c9e4034b356763e66cb17e9e728a15d49e999e82435b6b8f1d2c75df6 0.600000000000 1509547 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": 1040894, "vin": [ { "gen": { "height": 1040884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5209b96c9e4034b356763e66cb17e9e728a15d49e999e82435b6b8f1d2c75df6" } } ], "extra": [ 1, 101, 15, 127, 41, 81, 75, 111, 62, 248, 72, 200, 187, 164, 127, 180, 27, 40, 1, 51, 174, 253, 240, 39, 140, 69, 3, 28, 110, 84, 144, 189, 45, 2, 17, 0, 0, 0, 6, 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