Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ebb5e79ca802c3e2ff35d2dd169cc680b40537b1284546762a78576cea882d7

Tx prefix hash: c38c92f49debb633f7b22c735ced0ff9578b97c7ec9588b797c5fc451a1ad02f
Tx public key: 66c78de42e48ed50886aa0ae7c14a6bff6dbdd6f07726a0792e3486a3a808d84
Timestamp: 1737340899 Timestamp [UCT]: 2025-01-20 02:41:39 Age [y:d:h:m:s]: 00:053:13:21:18
Block: 1201123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38109 RingCT/type: yes/0
Extra: 0166c78de42e48ed50886aa0ae7c14a6bff6dbdd6f07726a0792e3486a3a808d840211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 437ef8ae4a5eeb53bdb35e5d82ea6d589798a37d873a40ad5f541b5a430f41b1 0.600000000000 1687772 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": 1201133, "vin": [ { "gen": { "height": 1201123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "437ef8ae4a5eeb53bdb35e5d82ea6d589798a37d873a40ad5f541b5a430f41b1" } } ], "extra": [ 1, 102, 199, 141, 228, 46, 72, 237, 80, 136, 106, 160, 174, 124, 20, 166, 191, 246, 219, 221, 111, 7, 114, 106, 7, 146, 227, 72, 106, 58, 128, 141, 132, 2, 17, 0, 0, 0, 6, 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