Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7bcf6cec16d40976c8957689af748b1b42b0273ed85624c2be89f127e9c107e

Tx prefix hash: 7c3b950d3ee62a964c7e31398d7a55734cbbe8738ed5735383e9c89eb3e415e8
Tx public key: c6adf59087d2b96c45e4b9f3f2d3650cd8ea6bbe6cc1e3486632a3c9efc91b3c
Timestamp: 1705394492 Timestamp [UCT]: 2024-01-16 08:41:32 Age [y:d:h:m:s]: 01:321:18:19:06
Block: 936447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 488823 RingCT/type: yes/0
Extra: 01c6adf59087d2b96c45e4b9f3f2d3650cd8ea6bbe6cc1e3486632a3c9efc91b3c02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09d30e3688da6793881c718b0232c0899f3fda9b437238c6bf5441f7b7a59a78 0.600000000000 1394473 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": 936457, "vin": [ { "gen": { "height": 936447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09d30e3688da6793881c718b0232c0899f3fda9b437238c6bf5441f7b7a59a78" } } ], "extra": [ 1, 198, 173, 245, 144, 135, 210, 185, 108, 69, 228, 185, 243, 242, 211, 101, 12, 216, 234, 107, 190, 108, 193, 227, 72, 102, 50, 163, 201, 239, 201, 27, 60, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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