Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 563c93f98385cf22b905b0ba037fb771d9de5e615dc12a4af00ef8d5859fe775

Tx prefix hash: 024de00d8f82fa3ed092d0ee5d9d35d8f842893882a731b6bd5536b0b5545052
Tx public key: aca77b3b9dc6d546c3a4a10ee9854869c3da20c897514c2a8572b7a85d7a94cb
Timestamp: 1636044023 Timestamp [UCT]: 2021-11-04 16:40:23 Age [y:d:h:m:s]: 02:334:16:18:17
Block: 367298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 756859 RingCT/type: yes/0
Extra: 01aca77b3b9dc6d546c3a4a10ee9854869c3da20c897514c2a8572b7a85d7a94cb02110000000d1154028c000000000000000000

1 output(s) for total of 37.238283298000 dcy

stealth address amount amount idx
00: 4c996e53a590efb29dc98de5cd1ed6eea98ca5a277732ee987731bdc0d8f6f42 37.238283298000 745310 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": 367308, "vin": [ { "gen": { "height": 367298 } } ], "vout": [ { "amount": 37238283298, "target": { "key": "4c996e53a590efb29dc98de5cd1ed6eea98ca5a277732ee987731bdc0d8f6f42" } } ], "extra": [ 1, 172, 167, 123, 59, 157, 198, 213, 70, 195, 164, 161, 14, 233, 133, 72, 105, 195, 218, 32, 200, 151, 81, 76, 42, 133, 114, 183, 168, 93, 122, 148, 203, 2, 17, 0, 0, 0, 13, 17, 84, 2, 140, 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