Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c99a3c6abfed986f479360650e3349596c04b682f09ec04af49314ae5abcfc30

Tx prefix hash: 68249476d2c29ebc9e84395853467edd2926d24e33f0db5394b1613a32c50792
Tx public key: 1e1882df193df25e5a06f09f66ee5ae7ecb6c588aad055d45a49ef96a82b3ff5
Timestamp: 1577200351 Timestamp [UCT]: 2019-12-24 15:12:31 Age [y:d:h:m:s]: 05:045:06:33:04
Block: 30814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1182094 RingCT/type: yes/0
Extra: 011e1882df193df25e5a06f09f66ee5ae7ecb6c588aad055d45a49ef96a82b3ff50211000000034943cd9f000000000000000000

1 output(s) for total of 485.178209669000 dcy

stealth address amount amount idx
00: 2dd7d4df2d5530e9d7bdab503dd4650caa2539ed6d3cbe20a131cbb19667b68c 485.178209669000 50864 of 0

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": 30824, "vin": [ { "gen": { "height": 30814 } } ], "vout": [ { "amount": 485178209669, "target": { "key": "2dd7d4df2d5530e9d7bdab503dd4650caa2539ed6d3cbe20a131cbb19667b68c" } } ], "extra": [ 1, 30, 24, 130, 223, 25, 61, 242, 94, 90, 6, 240, 159, 102, 238, 90, 231, 236, 182, 197, 136, 170, 208, 85, 212, 90, 73, 239, 150, 168, 43, 63, 245, 2, 17, 0, 0, 0, 3, 73, 67, 205, 159, 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