Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49d8434a3a5c4e642519102b0dd98123af9f6d1d3ceded925ea8e4e42bbe4ca3

Tx prefix hash: e0463d385c5cae875cc6460e25204e2c651660af375695e7423a1c7e17af6251
Tx public key: f31c00f2c79ba6178c48287693a0fe328a27ea1380e6572b7749f2cf0e33eec3
Timestamp: 1729710414 Timestamp [UCT]: 2024-10-23 19:06:54 Age [y:d:h:m:s]: 00:140:16:13:14
Block: 1138028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100347 RingCT/type: yes/0
Extra: 01f31c00f2c79ba6178c48287693a0fe328a27ea1380e6572b7749f2cf0e33eec30211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60bd49109fd47cdf4f72ead433816cdf31133ed5bafe2b89024a61697f8b0c9d 0.600000000000 1621629 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": 1138038, "vin": [ { "gen": { "height": 1138028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60bd49109fd47cdf4f72ead433816cdf31133ed5bafe2b89024a61697f8b0c9d" } } ], "extra": [ 1, 243, 28, 0, 242, 199, 155, 166, 23, 140, 72, 40, 118, 147, 160, 254, 50, 138, 39, 234, 19, 128, 230, 87, 43, 119, 73, 242, 207, 14, 51, 238, 195, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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