Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fee1340f35b1d9a176f2cbdae3cc6aa1c384c979676c59ef362ee0b588eb7b1

Tx prefix hash: 055baa1d736cdaf358da469d42e3f8bb89cf2a5073d733bc50c666190ba8718e
Tx public key: 527f9ace99e35d91e682c35f883ba0116c3a7e7c223ed128a025aab45f92e391
Timestamp: 1706794320 Timestamp [UCT]: 2024-02-01 13:32:00 Age [y:d:h:m:s]: 00:349:14:55:51
Block: 948052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250306 RingCT/type: yes/0
Extra: 01527f9ace99e35d91e682c35f883ba0116c3a7e7c223ed128a025aab45f92e3910211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 015fdfdc5ec6996dd0730b116a6ce21c82033e09b3eabe5e4f76c8a5a59e58f8 0.600000000000 1406424 of 15

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": 948062, "vin": [ { "gen": { "height": 948052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "015fdfdc5ec6996dd0730b116a6ce21c82033e09b3eabe5e4f76c8a5a59e58f8" } } ], "extra": [ 1, 82, 127, 154, 206, 153, 227, 93, 145, 230, 130, 195, 95, 136, 59, 160, 17, 108, 58, 126, 124, 34, 62, 209, 40, 160, 37, 170, 180, 95, 146, 227, 145, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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