Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14c7d8509b09a9148e291db9d171f14867634762df748fe7272994b40e6c4f3e

Tx prefix hash: 782121701e5c2f36d3a1d222f347a583d9b0e654e2f26be63a2a2b6efcbd573a
Tx public key: a8cc31799d85a049b0984e165030706ece6accff76167ceaf7f3999c937515be
Timestamp: 1578652305 Timestamp [UCT]: 2020-01-10 10:31:45 Age [y:d:h:m:s]: 04:353:23:39:07
Block: 42507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1142438 RingCT/type: yes/0
Extra: 01a8cc31799d85a049b0984e165030706ece6accff76167ceaf7f3999c937515be02110000000dd81c26c0000000000000000000

1 output(s) for total of 443.769558582000 dcy

stealth address amount amount idx
00: 1a067df48e80100240fbad7545e1c1d92d3e2f55363f965f881e56f73137aba5 443.769558582000 76628 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": 42517, "vin": [ { "gen": { "height": 42507 } } ], "vout": [ { "amount": 443769558582, "target": { "key": "1a067df48e80100240fbad7545e1c1d92d3e2f55363f965f881e56f73137aba5" } } ], "extra": [ 1, 168, 204, 49, 121, 157, 133, 160, 73, 176, 152, 78, 22, 80, 48, 112, 110, 206, 106, 204, 255, 118, 22, 124, 234, 247, 243, 153, 156, 147, 117, 21, 190, 2, 17, 0, 0, 0, 13, 216, 28, 38, 192, 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