Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfc4f38e438a719014ebc12b72a95f6b8c9179ea74ab0e29aae50cd36958884d

Tx prefix hash: 6b242d21556ec3dca426d979d68b114ccc092123dad9a957b2b7e90a1def5b7d
Tx public key: e8a09cc80ec1b8f98c555adc965fe47ae2cedd61d23738b07f848c4af2804aac
Timestamp: 1735297712 Timestamp [UCT]: 2024-12-27 11:08:32 Age [y:d:h:m:s]: 01:036:01:40:49
Block: 1184258 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284076 RingCT/type: yes/0
Extra: 01e8a09cc80ec1b8f98c555adc965fe47ae2cedd61d23738b07f848c4af2804aac021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 327b2114a42f06ba6e179201d5d5685b2c7221faaabf197c02e9d31be8ae1163 0.600000000000 1670713 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": 1184268, "vin": [ { "gen": { "height": 1184258 } } ], "vout": [ { "amount": 600000000, "target": { "key": "327b2114a42f06ba6e179201d5d5685b2c7221faaabf197c02e9d31be8ae1163" } } ], "extra": [ 1, 232, 160, 156, 200, 14, 193, 184, 249, 140, 85, 90, 220, 150, 95, 228, 122, 226, 206, 221, 97, 210, 55, 56, 176, 127, 132, 140, 74, 242, 128, 74, 172, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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