Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 635d6d712e6ae3b01274ca099e65ad0db467079a4701dbbfb43e0697d4310c85

Tx prefix hash: 0346f94b052f2440da767791301adef1193087c521255e36e8d4230f525792f8
Tx public key: 33701ee6b32f29e91d39d0626ff5d06ea6c99263f6d5ba6f16382c352b428402
Timestamp: 1681181346 Timestamp [UCT]: 2023-04-11 02:49:06 Age [y:d:h:m:s]: 01:266:12:25:43
Block: 735967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 451992 RingCT/type: yes/0
Extra: 0133701ee6b32f29e91d39d0626ff5d06ea6c99263f6d5ba6f16382c352b4284020211000000045029cbac000000000000000000

1 output(s) for total of 2.235815889000 dcy

stealth address amount amount idx
00: 6ab75f3dd8be4f2c5f9804350ca4e9a1bc9291f068a4dc93fc0fa3f277af26bf 2.235815889000 1182340 of 0

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": 735977, "vin": [ { "gen": { "height": 735967 } } ], "vout": [ { "amount": 2235815889, "target": { "key": "6ab75f3dd8be4f2c5f9804350ca4e9a1bc9291f068a4dc93fc0fa3f277af26bf" } } ], "extra": [ 1, 51, 112, 30, 230, 179, 47, 41, 233, 29, 57, 208, 98, 111, 245, 208, 110, 166, 201, 146, 99, 246, 213, 186, 111, 22, 56, 44, 53, 43, 66, 132, 2, 2, 17, 0, 0, 0, 4, 80, 41, 203, 172, 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