Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a19e8fe444b258c4b94eafa3ab6d4c54b7257fe72580882bb8feecb8484a9eb2

Tx prefix hash: 9bad4fb41c67d19a710c5eebc665560bb104faa6616169b1496ba52297a4c270
Tx public key: c108f8101bcc67dc5fedeb34e3b4c56b3ee612e784c51757d928ae22c0cb858f
Timestamp: 1633685420 Timestamp [UCT]: 2021-10-08 09:30:20 Age [y:d:h:m:s]: 03:137:00:27:11
Block: 349044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 874946 RingCT/type: yes/0
Extra: 01c108f8101bcc67dc5fedeb34e3b4c56b3ee612e784c51757d928ae22c0cb858f0211000000018d0de867000000000000000000

1 output(s) for total of 42.805556908000 dcy

stealth address amount amount idx
00: c61325a8101e5d8b0e89e9cd3cf5cab7cbd49e797807ccfcdac85457fb3de3a0 42.805556908000 714677 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": 349054, "vin": [ { "gen": { "height": 349044 } } ], "vout": [ { "amount": 42805556908, "target": { "key": "c61325a8101e5d8b0e89e9cd3cf5cab7cbd49e797807ccfcdac85457fb3de3a0" } } ], "extra": [ 1, 193, 8, 248, 16, 27, 204, 103, 220, 95, 237, 235, 52, 227, 180, 197, 107, 62, 230, 18, 231, 132, 197, 23, 87, 217, 40, 174, 34, 192, 203, 133, 143, 2, 17, 0, 0, 0, 1, 141, 13, 232, 103, 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