Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7989830c4d806e77261ef2d4678f8a0c9f5eef0187474c227f56e714e15d534d

Tx prefix hash: 81e5151e58ca4ae7303659b3ac10f99b4e01935f3982af2d0794926547869b77
Tx public key: 52f6a26756696ea7b14a4e8fc883cc9fe5732e117f8232a9c65f167ce0bbf4c9
Timestamp: 1738225165 Timestamp [UCT]: 2025-01-30 08:19:25 Age [y:d:h:m:s]: 00:143:11:29:17
Block: 1208229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102414 RingCT/type: yes/0
Extra: 0152f6a26756696ea7b14a4e8fc883cc9fe5732e117f8232a9c65f167ce0bbf4c90211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45e356201237d5c80790a4d59713b8bcc006bdb5451e8ea48b3a97d383690df2 0.600000000000 1694960 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": 1208239, "vin": [ { "gen": { "height": 1208229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45e356201237d5c80790a4d59713b8bcc006bdb5451e8ea48b3a97d383690df2" } } ], "extra": [ 1, 82, 246, 162, 103, 86, 105, 110, 167, 177, 74, 78, 143, 200, 131, 204, 159, 229, 115, 46, 17, 127, 130, 50, 169, 198, 95, 22, 124, 224, 187, 244, 201, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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