Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebbd69597dfe457c8dba95f20d085f549dfd4c87f3c34099e1dd38aac205efc4

Tx prefix hash: 59ec952ee4acf9fa17b92846e7076c0d3020479946669e71f1c84571566672e2
Tx public key: e6b9e5a695a6ad637c312a48aaec56e9b533db143db537ccf3782a391c3a8dee
Timestamp: 1728148302 Timestamp [UCT]: 2024-10-05 17:11:42 Age [y:d:h:m:s]: 00:162:18:16:39
Block: 1125112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116135 RingCT/type: yes/0
Extra: 01e6b9e5a695a6ad637c312a48aaec56e9b533db143db537ccf3782a391c3a8dee02110000001091e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a03dbbcd3972400cd2c5aecf5cccf4c9d20781116f1a3f487ba5bdd0dbf9bf0b 0.600000000000 1607785 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": 1125122, "vin": [ { "gen": { "height": 1125112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a03dbbcd3972400cd2c5aecf5cccf4c9d20781116f1a3f487ba5bdd0dbf9bf0b" } } ], "extra": [ 1, 230, 185, 229, 166, 149, 166, 173, 99, 124, 49, 42, 72, 170, 236, 86, 233, 181, 51, 219, 20, 61, 181, 55, 204, 243, 120, 42, 57, 28, 58, 141, 238, 2, 17, 0, 0, 0, 16, 145, 225, 60, 4, 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