Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9fbb46ee903c8a94554b841e2c62f0b68a898e98e97bbdc1ad2b99c0652603b

Tx prefix hash: 9c1d36fb7332eba15d6dda145b5b3ed8a04401842cec5509a6867a5b53181790
Tx public key: 4175fd51ac556882198dbbdaa8d1a71bb1cee033c51cb136474fade1049ce8d9
Timestamp: 1720193248 Timestamp [UCT]: 2024-07-05 15:27:28 Age [y:d:h:m:s]: 00:277:12:15:08
Block: 1059150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198285 RingCT/type: yes/0
Extra: 014175fd51ac556882198dbbdaa8d1a71bb1cee033c51cb136474fade1049ce8d902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3402a4534d429343eee5e015c49880d522ba3649e4a8a8a83f477e3fdde17f22 0.600000000000 1529611 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": 1059160, "vin": [ { "gen": { "height": 1059150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3402a4534d429343eee5e015c49880d522ba3649e4a8a8a83f477e3fdde17f22" } } ], "extra": [ 1, 65, 117, 253, 81, 172, 85, 104, 130, 25, 141, 187, 218, 168, 209, 167, 27, 177, 206, 224, 51, 197, 28, 177, 54, 71, 79, 173, 225, 4, 156, 232, 217, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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