Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c39cfe72f00b404e076bc57c4ebac7e12eea286bfe0e07c3de74b9036924d00f

Tx prefix hash: 37954045a09d16413692a068b5ea5cd14385992f3090bd4282fb1d75cc06e07a
Tx public key: 22eb0aadade05e31d7be547a3a35f8f27bb55e69df72b186bac371079dc7dcc7
Timestamp: 1727738459 Timestamp [UCT]: 2024-09-30 23:20:59 Age [y:d:h:m:s]: 00:055:04:04:38
Block: 1121716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39417 RingCT/type: yes/0
Extra: 0122eb0aadade05e31d7be547a3a35f8f27bb55e69df72b186bac371079dc7dcc7021100000001e914dd15000000000000000000

1 output(s) for total of 0.600200000000 dcy

stealth address amount amount idx
00: c2df41c563dbb58c6a8f0cde1b62990059976f7cc400fccc1c99338f847c2cbe 0.600200000000 1604037 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": 1121726, "vin": [ { "gen": { "height": 1121716 } } ], "vout": [ { "amount": 600200000, "target": { "key": "c2df41c563dbb58c6a8f0cde1b62990059976f7cc400fccc1c99338f847c2cbe" } } ], "extra": [ 1, 34, 235, 10, 173, 173, 224, 94, 49, 215, 190, 84, 122, 58, 53, 248, 242, 123, 181, 94, 105, 223, 114, 177, 134, 186, 195, 113, 7, 157, 199, 220, 199, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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