Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f1b8a669989c3aad79392bf9469816ecde4bb4f3b179f0952117934112b9fe2

Tx prefix hash: 1b941032a04a5552c0fb55d4d6050b859bda16dafe4ff9e79a95be4c9c01df16
Tx public key: 17605a277e71e99b151cf3b24ee13f24b22e141aaf4d3467da1e832a130a19b9
Timestamp: 1708294192 Timestamp [UCT]: 2024-02-18 22:09:52 Age [y:d:h:m:s]: 01:074:06:10:18
Block: 960513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314109 RingCT/type: yes/0
Extra: 0117605a277e71e99b151cf3b24ee13f24b22e141aaf4d3467da1e832a130a19b902110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a7d722b4b1093b2eae9ac3a245ae86f0c84e57f47d2bde6057740379fcfa89d 0.600000000000 1420084 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": 960523, "vin": [ { "gen": { "height": 960513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a7d722b4b1093b2eae9ac3a245ae86f0c84e57f47d2bde6057740379fcfa89d" } } ], "extra": [ 1, 23, 96, 90, 39, 126, 113, 233, 155, 21, 28, 243, 178, 78, 225, 63, 36, 178, 46, 20, 26, 175, 77, 52, 103, 218, 30, 131, 42, 19, 10, 25, 185, 2, 17, 0, 0, 0, 4, 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