Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b114638982a13c2cac06e0ed5ef440d9e5ca95e3e132e63ffe821d8cd6bdf4e7

Tx prefix hash: 54c9b40aafe9b4504f254edc7aa3d5739e276f008a14811c54b481e703632423
Tx public key: 1385955ace6be4c4cb9ad74d8355864f8933ec76fd80a1f988fe91acf04fe23a
Timestamp: 1709840058 Timestamp [UCT]: 2024-03-07 19:34:18 Age [y:d:h:m:s]: 01:090:00:53:57
Block: 973335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325378 RingCT/type: yes/0
Extra: 011385955ace6be4c4cb9ad74d8355864f8933ec76fd80a1f988fe91acf04fe23a0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1be3ce05d20b95872ac958b1eb8a23c83097811e37c7e0238f5fd331b83f47c5 0.600000000000 1433270 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": 973345, "vin": [ { "gen": { "height": 973335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1be3ce05d20b95872ac958b1eb8a23c83097811e37c7e0238f5fd331b83f47c5" } } ], "extra": [ 1, 19, 133, 149, 90, 206, 107, 228, 196, 203, 154, 215, 77, 131, 85, 134, 79, 137, 51, 236, 118, 253, 128, 161, 249, 136, 254, 145, 172, 240, 79, 226, 58, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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