Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 879a960a79875c1205fd772d8fc21f18e0986ea9230be3b0e4105f781dc5944b

Tx prefix hash: d8bc0e706e1eb4c1d99e8c0a25288d440ce3675c214e11c3f7b48c26e87d166f
Tx public key: ca3bd851ee051692413a8985cb17b3eaa6c582243882541271cff8fd88676938
Timestamp: 1684776234 Timestamp [UCT]: 2023-05-22 17:23:54 Age [y:d:h:m:s]: 02:172:11:03:41
Block: 765790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 643051 RingCT/type: yes/0
Extra: 01ca3bd851ee051692413a8985cb17b3eaa6c582243882541271cff8fd8867693802110000000333af99f4000000000000000000

1 output(s) for total of 1.780819963000 dcy

stealth address amount amount idx
00: d9039fc077332e58cbd9b8985dee4772d6e9d33ae2eda48fa861af7932ba7f7a 1.780819963000 1214797 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": 765800, "vin": [ { "gen": { "height": 765790 } } ], "vout": [ { "amount": 1780819963, "target": { "key": "d9039fc077332e58cbd9b8985dee4772d6e9d33ae2eda48fa861af7932ba7f7a" } } ], "extra": [ 1, 202, 59, 216, 81, 238, 5, 22, 146, 65, 58, 137, 133, 203, 23, 179, 234, 166, 197, 130, 36, 56, 130, 84, 18, 113, 207, 248, 253, 136, 103, 105, 56, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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