Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0624c03fda242f42d5e88d83105add455a8e254fbde89c7ad69ecd7b4be7d90

Tx prefix hash: e625ce0fbc64043a3df940eab51100c21cb63b12f001eafcf67a66243c0d58b2
Tx public key: 3ae90cb7b687f1a0d6c4750074aa324267a4031c0d896a25bf79ef1c1d894488
Timestamp: 1581209094 Timestamp [UCT]: 2020-02-09 00:44:54 Age [y:d:h:m:s]: 04:342:05:58:52
Block: 60959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1136756 RingCT/type: yes/0
Extra: 013ae90cb7b687f1a0d6c4750074aa324267a4031c0d896a25bf79ef1c1d8944880211000000174943cd9f000000000000000000

1 output(s) for total of 385.494640653000 dcy

stealth address amount amount idx
00: 1c46413b7fe68e4168d7108cd019c9a00427eb2fa1c033313dee24cc3fc4aa19 385.494640653000 112374 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": 60969, "vin": [ { "gen": { "height": 60959 } } ], "vout": [ { "amount": 385494640653, "target": { "key": "1c46413b7fe68e4168d7108cd019c9a00427eb2fa1c033313dee24cc3fc4aa19" } } ], "extra": [ 1, 58, 233, 12, 183, 182, 135, 241, 160, 214, 196, 117, 0, 116, 170, 50, 66, 103, 164, 3, 28, 13, 137, 106, 37, 191, 121, 239, 28, 29, 137, 68, 136, 2, 17, 0, 0, 0, 23, 73, 67, 205, 159, 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