Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35a49921220da7ea77eec4d6779563fdc9d32a7e7cbc16ac9a60095fe8bab087

Tx prefix hash: 66d8b9f2139c9065d784a5338ab957190db1e5345b27327df86eb8c58b4d1d57
Tx public key: 89403f768d8b5975be48bc82bd1fbd5acb300a017d54d6ae87203ef41285bb2a
Timestamp: 1713042927 Timestamp [UCT]: 2024-04-13 21:15:27 Age [y:d:h:m:s]: 00:349:14:26:11
Block: 999859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249953 RingCT/type: yes/0
Extra: 0189403f768d8b5975be48bc82bd1fbd5acb300a017d54d6ae87203ef41285bb2a021100000004679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d0674d353c3df35e3ea9cafbe9c7753e8553cc4c5e818ff450aeea944b378f9 0.600000000000 1460347 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": 999869, "vin": [ { "gen": { "height": 999859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d0674d353c3df35e3ea9cafbe9c7753e8553cc4c5e818ff450aeea944b378f9" } } ], "extra": [ 1, 137, 64, 63, 118, 141, 139, 89, 117, 190, 72, 188, 130, 189, 31, 189, 90, 203, 48, 10, 1, 125, 84, 214, 174, 135, 32, 62, 244, 18, 133, 187, 42, 2, 17, 0, 0, 0, 4, 103, 154, 138, 129, 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