Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 308c102370451a973701301e6b49cceef9426d6708fee6474e03c446057b6b66

Tx prefix hash: 84d81b5fbe4f292f295b9e2b09f78bc64592c813847df3f4e26f6874c64c9436
Tx public key: 65b7ceb42866097827a396f181f98fb909cef9440d0da46163d3ea666640adda
Timestamp: 1696099134 Timestamp [UCT]: 2023-09-30 18:38:54 Age [y:d:h:m:s]: 01:235:14:07:51
Block: 859607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429470 RingCT/type: yes/0
Extra: 0165b7ceb42866097827a396f181f98fb909cef9440d0da46163d3ea666640adda0211000000034b8f5122000000000000000000

1 output(s) for total of 0.870492857000 dcy

stealth address amount amount idx
00: f50c12095fd5c213cb5c2a09f72318fa545fbaa1d353c956ba1bf88c231ef897 0.870492857000 1313841 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": 859617, "vin": [ { "gen": { "height": 859607 } } ], "vout": [ { "amount": 870492857, "target": { "key": "f50c12095fd5c213cb5c2a09f72318fa545fbaa1d353c956ba1bf88c231ef897" } } ], "extra": [ 1, 101, 183, 206, 180, 40, 102, 9, 120, 39, 163, 150, 241, 129, 249, 143, 185, 9, 206, 249, 68, 13, 13, 164, 97, 99, 211, 234, 102, 102, 64, 173, 218, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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