Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fda7b8b0693d1290bf3c18facdb7e54dbe9f7e39d2176a6dc7622432e5374668

Tx prefix hash: b7a05ab86909a72e3ec72fab415d456289d6e61e109c152f45b4cbedba3f893c
Tx public key: 4487f89ce54182fd870b884777fccc30a45731a9d1886cb3652bd5e81e6bad33
Timestamp: 1612130433 Timestamp [UCT]: 2021-01-31 22:00:33 Age [y:d:h:m:s]: 03:328:08:52:17
Block: 189318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 993391 RingCT/type: yes/0
Extra: 014487f89ce54182fd870b884777fccc30a45731a9d1886cb3652bd5e81e6bad33021100000c10b9b01d0b000000000000000000

1 output(s) for total of 144.785990623000 dcy

stealth address amount amount idx
00: e20b896318fdbdcf18c699cf2f551bbc8fc0c7d73277a7dd4fa364759ec5ef8a 144.785990623000 378149 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": 189328, "vin": [ { "gen": { "height": 189318 } } ], "vout": [ { "amount": 144785990623, "target": { "key": "e20b896318fdbdcf18c699cf2f551bbc8fc0c7d73277a7dd4fa364759ec5ef8a" } } ], "extra": [ 1, 68, 135, 248, 156, 229, 65, 130, 253, 135, 11, 136, 71, 119, 252, 204, 48, 164, 87, 49, 169, 209, 136, 108, 179, 101, 43, 213, 232, 30, 107, 173, 51, 2, 17, 0, 0, 12, 16, 185, 176, 29, 11, 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