Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 102692ce650d7e87c229c2f52d2dec0c8183333d4cb26d802ce52a45162f2795

Tx prefix hash: bd0ca47c034279560b329e58eade2d987b6dcd9563bfb8428afc93115c652b9d
Tx public key: a972b54b9658d8742a4e232938b9ba74241eefe536dd0b3f271f05657d2d5c78
Timestamp: 1717279797 Timestamp [UCT]: 2024-06-01 22:09:57 Age [y:d:h:m:s]: 00:290:12:02:17
Block: 1035019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207618 RingCT/type: yes/0
Extra: 01a972b54b9658d8742a4e232938b9ba74241eefe536dd0b3f271f05657d2d5c78021100000003e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f85d04a7ef035d4d9ab38ba05b10b79c6b8509da097192766ce4921c0f0772c 0.600000000000 1503538 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": 1035029, "vin": [ { "gen": { "height": 1035019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f85d04a7ef035d4d9ab38ba05b10b79c6b8509da097192766ce4921c0f0772c" } } ], "extra": [ 1, 169, 114, 181, 75, 150, 88, 216, 116, 42, 78, 35, 41, 56, 185, 186, 116, 36, 30, 239, 229, 54, 221, 11, 63, 39, 31, 5, 101, 125, 45, 92, 120, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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