Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe6632c48a243e84aba5d4e5908a069fbea8c8304fe2c0a5e20801afe54a2881

Tx prefix hash: 2de9bd6ac8707bee0f96d58ac6772af0bfd723c034ace0fdefe4b7622855b3f1
Tx public key: a9dfc1fd087a8b134bec2d4c01652175cb18932197de5af148b671efa6567e02
Timestamp: 1733135291 Timestamp [UCT]: 2024-12-02 10:28:11 Age [y:d:h:m:s]: 00:120:10:00:06
Block: 1166356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85846 RingCT/type: yes/0
Extra: 01a9dfc1fd087a8b134bec2d4c01652175cb18932197de5af148b671efa6567e020211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66169bb4dc1d610a9782a7c809b7cebb4fc73f196cf8bf7e6cae42839505b37c 0.600000000000 1652043 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": 1166366, "vin": [ { "gen": { "height": 1166356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66169bb4dc1d610a9782a7c809b7cebb4fc73f196cf8bf7e6cae42839505b37c" } } ], "extra": [ 1, 169, 223, 193, 253, 8, 122, 139, 19, 75, 236, 45, 76, 1, 101, 33, 117, 203, 24, 147, 33, 151, 222, 90, 241, 72, 182, 113, 239, 166, 86, 126, 2, 2, 17, 0, 0, 0, 3, 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