Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 205b0779b515eba940869486ce92e877decbf75f5971623b584fd204db778a99

Tx prefix hash: 62715083fdccf0919bd061ad1e99bb0b4f90b54726efc043646b71b7aef0a932
Tx public key: 0fa8e335fa7a08f52593af1ab6f22b3a4bd39dd7bdb81e8fd6f36b3eb7c94e28
Timestamp: 1609022100 Timestamp [UCT]: 2020-12-26 22:35:00 Age [y:d:h:m:s]: 04:065:00:47:11
Block: 169995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1059408 RingCT/type: yes/0
Extra: 010fa8e335fa7a08f52593af1ab6f22b3a4bd39dd7bdb81e8fd6f36b3eb7c94e280211000000a44ea414e5000000000000000000

1 output(s) for total of 167.790237216000 dcy

stealth address amount amount idx
00: dd9b67f105293e380518196b2f6498a6fc2b86948e9c4fe441bbeb5e2fe78d6d 167.790237216000 318170 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": 170005, "vin": [ { "gen": { "height": 169995 } } ], "vout": [ { "amount": 167790237216, "target": { "key": "dd9b67f105293e380518196b2f6498a6fc2b86948e9c4fe441bbeb5e2fe78d6d" } } ], "extra": [ 1, 15, 168, 227, 53, 250, 122, 8, 245, 37, 147, 175, 26, 182, 242, 43, 58, 75, 211, 157, 215, 189, 184, 30, 143, 214, 243, 107, 62, 183, 201, 78, 40, 2, 17, 0, 0, 0, 164, 78, 164, 20, 229, 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