Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ae403ddf5c31266c26e088ffa1d06696966af59e748e4de3fed62cee82fc8d3

Tx prefix hash: ffe0cf4477da4782d55a6e3fb6e3317b4f855774051d02770f09597bd2ca95d3
Tx public key: 2c7ee1d533b562f2c05e99b7795bf7aa4edd72d385b732b095cda6526eb8edc8
Timestamp: 1732399187 Timestamp [UCT]: 2024-11-23 21:59:47 Age [y:d:h:m:s]: 00:130:15:06:57
Block: 1160248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93175 RingCT/type: yes/0
Extra: 012c7ee1d533b562f2c05e99b7795bf7aa4edd72d385b732b095cda6526eb8edc8021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43bcefd1537a1c82f44fa17648bb52381a85f4c91f1760d838bdedb5853c3bd1 0.600000000000 1645891 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": 1160258, "vin": [ { "gen": { "height": 1160248 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43bcefd1537a1c82f44fa17648bb52381a85f4c91f1760d838bdedb5853c3bd1" } } ], "extra": [ 1, 44, 126, 225, 213, 51, 181, 98, 242, 192, 94, 153, 183, 121, 91, 247, 170, 78, 221, 114, 211, 133, 183, 50, 176, 149, 205, 166, 82, 110, 184, 237, 200, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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