Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be1f97ca259aea6087f8c41f6273940abed1770fdf605266f83c35363529303a

Tx prefix hash: b081a06e2747a47ff985e7500ff66410034b84b2ded0c7bbe5bb85ddf91e3f61
Tx public key: 61cb84e8d5fee6b51a79631ac849dad85d84ae509e460741f486032e5e4c81b6
Timestamp: 1736270769 Timestamp [UCT]: 2025-01-07 17:26:09 Age [y:d:h:m:s]: 00:093:05:42:15
Block: 1192313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66418 RingCT/type: yes/0
Extra: 0161cb84e8d5fee6b51a79631ac849dad85d84ae509e460741f486032e5e4c81b6021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9ca17189fe5aa7a70b671bcf15bb70b8d6c1ba8f95d3083213942f5bd50c5b3 0.600000000000 1678862 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": 1192323, "vin": [ { "gen": { "height": 1192313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9ca17189fe5aa7a70b671bcf15bb70b8d6c1ba8f95d3083213942f5bd50c5b3" } } ], "extra": [ 1, 97, 203, 132, 232, 213, 254, 230, 181, 26, 121, 99, 26, 200, 73, 218, 216, 93, 132, 174, 80, 158, 70, 7, 65, 244, 134, 3, 46, 94, 76, 129, 182, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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