Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cfbcfee35d37fe0d221c238ec1ea19b05313e576b7a158c32d0db1c6fc71c66

Tx prefix hash: 440455d33ee0f42d3f3a76de21b11dcd28e90692c85390068efd23049e625779
Tx public key: 0d779da03914a8ddd24a6a6eab99a577e2de241742923458b47f8867d90152b9
Timestamp: 1735488216 Timestamp [UCT]: 2024-12-29 16:03:36 Age [y:d:h:m:s]: 00:171:02:31:20
Block: 1185824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122003 RingCT/type: yes/0
Extra: 010d779da03914a8ddd24a6a6eab99a577e2de241742923458b47f8867d90152b90211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f91611a0c48c06d35568b458320e566814c3af7c413dd1acca942651d4b7bf8 0.600000000000 1672299 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": 1185834, "vin": [ { "gen": { "height": 1185824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f91611a0c48c06d35568b458320e566814c3af7c413dd1acca942651d4b7bf8" } } ], "extra": [ 1, 13, 119, 157, 160, 57, 20, 168, 221, 210, 74, 106, 110, 171, 153, 165, 119, 226, 222, 36, 23, 66, 146, 52, 88, 180, 127, 136, 103, 217, 1, 82, 185, 2, 17, 0, 0, 0, 1, 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