Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e1c9f7ab2981139605e542e64fa450a8efcd8e722e159d4b26f42699d1fbc77

Tx prefix hash: 1b2164e547d40c7f7cb09b3ea907d743d9957bcf134ec00ecd66af95df6dbb82
Tx public key: 97d7a4cbb20096a42e6e8ec2eb3e4042644e7577f3e2e5fbfd499740a8cf2d08
Timestamp: 1706922159 Timestamp [UCT]: 2024-02-03 01:02:39 Age [y:d:h:m:s]: 01:071:23:06:26
Block: 949119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312501 RingCT/type: yes/0
Extra: 0197d7a4cbb20096a42e6e8ec2eb3e4042644e7577f3e2e5fbfd499740a8cf2d080211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 082c68e13aafc0f8f43f461c502f9655f2d2eb5694c433457cab5c5e9a67cd1d 0.600000000000 1407641 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": 949129, "vin": [ { "gen": { "height": 949119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "082c68e13aafc0f8f43f461c502f9655f2d2eb5694c433457cab5c5e9a67cd1d" } } ], "extra": [ 1, 151, 215, 164, 203, 178, 0, 150, 164, 46, 110, 142, 194, 235, 62, 64, 66, 100, 78, 117, 119, 243, 226, 229, 251, 253, 73, 151, 64, 168, 207, 45, 8, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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