Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23d657aeea1a9cd944ba5185b7338681f9d129b9b660dbeba9a0c1cdd052c76d

Tx prefix hash: 6896ae5b8acf6ee0c239fb40d54e18b5a92ff602c0dab3c2dceaa96311a98da9
Tx public key: 3796093beff104da3334f961e782d912c6b1df40232bd31e774d1a9f4b532268
Timestamp: 1716184446 Timestamp [UCT]: 2024-05-20 05:54:06 Age [y:d:h:m:s]: 00:329:21:09:43
Block: 1025928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235779 RingCT/type: yes/0
Extra: 013796093beff104da3334f961e782d912c6b1df40232bd31e774d1a9f4b53226802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fee56371ebd938529696faab8e9dda322e80abf419aea9c8076cca6fb1e6da3 0.600000000000 1492729 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": 1025938, "vin": [ { "gen": { "height": 1025928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fee56371ebd938529696faab8e9dda322e80abf419aea9c8076cca6fb1e6da3" } } ], "extra": [ 1, 55, 150, 9, 59, 239, 241, 4, 218, 51, 52, 249, 97, 231, 130, 217, 18, 198, 177, 223, 64, 35, 43, 211, 30, 119, 77, 26, 159, 75, 83, 34, 104, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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