Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44c95e3cc4888d182ba9ceae4f67f761f9eb7631788cd0c5aaf9229125833c9e

Tx prefix hash: 1697bcf2a2946c0e7a95a482c6650ea9a1a6aae337c8c5bbc7bcef66ad9e3b5f
Tx public key: a0b62527e4624ca0a16a3bd030118d6abf8860e0cbc0ebdb3899fa7559b69242
Timestamp: 1721382433 Timestamp [UCT]: 2024-07-19 09:47:13 Age [y:d:h:m:s]: 00:252:21:15:59
Block: 1069032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180636 RingCT/type: yes/0
Extra: 01a0b62527e4624ca0a16a3bd030118d6abf8860e0cbc0ebdb3899fa7559b69242021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf71166fc0b1c5bdea2176784783eeec1dd496fa1a92e37946970292d63fef3a 0.600000000000 1540295 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": 1069042, "vin": [ { "gen": { "height": 1069032 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf71166fc0b1c5bdea2176784783eeec1dd496fa1a92e37946970292d63fef3a" } } ], "extra": [ 1, 160, 182, 37, 39, 228, 98, 76, 160, 161, 106, 59, 208, 48, 17, 141, 106, 191, 136, 96, 224, 203, 192, 235, 219, 56, 153, 250, 117, 89, 182, 146, 66, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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