Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05b8b89f005b6ffa3ae78251b9bb524f76158e7f18d79267feaf94c459d92e9f

Tx prefix hash: 56dd4de973bd3868a760f16c96753e6d6398af69b14073d5a4f43ae85c554286
Tx public key: 1d47dc861f10f328620a98343aa79a866f42c811ec5defd40f5b9e211e2c9905
Timestamp: 1736209999 Timestamp [UCT]: 2025-01-07 00:33:19 Age [y:d:h:m:s]: 00:069:11:57:13
Block: 1191801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49468 RingCT/type: yes/0
Extra: 011d47dc861f10f328620a98343aa79a866f42c811ec5defd40f5b9e211e2c9905021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ccd2967ebc83b5166c18f658f879b8e995037e71434ce0429467e1eb0931abf0 0.600000000000 1678342 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": 1191811, "vin": [ { "gen": { "height": 1191801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccd2967ebc83b5166c18f658f879b8e995037e71434ce0429467e1eb0931abf0" } } ], "extra": [ 1, 29, 71, 220, 134, 31, 16, 243, 40, 98, 10, 152, 52, 58, 167, 154, 134, 111, 66, 200, 17, 236, 93, 239, 212, 15, 91, 158, 33, 30, 44, 153, 5, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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