Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 987d0679cfc7d3a40e6ed7f76bfcc673f3dfd39b4075fa2ebaab6c6300e78e61

Tx prefix hash: 5e5e8d0d0e735ec0c03bb62a9d0ed23873d5c4f97de1bb30f8381ec7fdf0f29b
Tx public key: 34e8f4777b4779ca613693c9fb38cf7ba1443f2d8be05360e405c5fc79bff616
Timestamp: 1734700877 Timestamp [UCT]: 2024-12-20 13:21:17 Age [y:d:h:m:s]: 00:094:05:51:08
Block: 1179347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67105 RingCT/type: yes/0
Extra: 0134e8f4777b4779ca613693c9fb38cf7ba1443f2d8be05360e405c5fc79bff6160211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c5236934b7707f9a0c5d8a503f2af6e14c9b3b97f51015f6a674401ed80c33d 0.600000000000 1665742 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": 1179357, "vin": [ { "gen": { "height": 1179347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c5236934b7707f9a0c5d8a503f2af6e14c9b3b97f51015f6a674401ed80c33d" } } ], "extra": [ 1, 52, 232, 244, 119, 123, 71, 121, 202, 97, 54, 147, 201, 251, 56, 207, 123, 161, 68, 63, 45, 139, 224, 83, 96, 228, 5, 197, 252, 121, 191, 246, 22, 2, 17, 0, 0, 0, 9, 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