Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29c4feb9b67e9b88faba0b15560c52af72f8d4771a0afa180fbe94bb3de98cc5

Tx prefix hash: b99e1b894d6c4192ef6852a71115b437c4536f192386a1e4bc9f0e3dddcc9933
Tx public key: c402758c18f363d085943f9fbb3c25c50fdd7f29b9ba684e702ed132c691c9ad
Timestamp: 1723880074 Timestamp [UCT]: 2024-08-17 07:34:34 Age [y:d:h:m:s]: 00:235:14:18:21
Block: 1089735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168241 RingCT/type: yes/0
Extra: 01c402758c18f363d085943f9fbb3c25c50fdd7f29b9ba684e702ed132c691c9ad02110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf4c25608e0eb35729bfb844a0f9972513c05b2e80c5d3adc93c3cc7eaf753d4 0.600000000000 1564358 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": 1089745, "vin": [ { "gen": { "height": 1089735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf4c25608e0eb35729bfb844a0f9972513c05b2e80c5d3adc93c3cc7eaf753d4" } } ], "extra": [ 1, 196, 2, 117, 140, 24, 243, 99, 208, 133, 148, 63, 159, 187, 60, 37, 197, 15, 221, 127, 41, 185, 186, 104, 78, 112, 46, 209, 50, 198, 145, 201, 173, 2, 17, 0, 0, 0, 11, 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