Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50505cd34d7db42e2fced95316e5783e2e6f4039a04e4199db8fc4067d4e6e77

Tx prefix hash: 290d0b863754acb8cc0465defdd9c5307e6abfc129a69a891d4315c11e4f03da
Tx public key: 10c2f9e782085ec72288657911bbd61acf42b3cb5b8d8bdda61f521e3f46be36
Timestamp: 1702965554 Timestamp [UCT]: 2023-12-19 05:59:14 Age [y:d:h:m:s]: 01:118:02:30:41
Block: 916338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345534 RingCT/type: yes/0
Extra: 0110c2f9e782085ec72288657911bbd61acf42b3cb5b8d8bdda61f521e3f46be3602110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7da722c9bec9fea243c6cdc4c97521dc932fce02aad5529d3f3d56210fa22400 0.600000000000 1373838 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": 916348, "vin": [ { "gen": { "height": 916338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7da722c9bec9fea243c6cdc4c97521dc932fce02aad5529d3f3d56210fa22400" } } ], "extra": [ 1, 16, 194, 249, 231, 130, 8, 94, 199, 34, 136, 101, 121, 17, 187, 214, 26, 207, 66, 179, 203, 91, 141, 139, 221, 166, 31, 82, 30, 63, 70, 190, 54, 2, 17, 0, 0, 0, 1, 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