Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f18196e33b1b0c639b9a9c1f76a838fcca87dcbe8dd753bca96bc872eecbf9d

Tx prefix hash: 09e46f5b7ca4643bf5daac9d51244a965b6ab1c9e7007d423dd5631f28ef0f79
Tx public key: da63f49a1b3836804ee566f99878dbc7641cba06617bc67a491a703b7c05f722
Timestamp: 1708554517 Timestamp [UCT]: 2024-02-21 22:28:37 Age [y:d:h:m:s]: 01:058:12:12:37
Block: 962669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302841 RingCT/type: yes/0
Extra: 01da63f49a1b3836804ee566f99878dbc7641cba06617bc67a491a703b7c05f72202110000000c0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5797c2767fb32a1bc26acb2380c1ceb284b22b30d1b4f9e5881708a375ab1e1 0.600000000000 1422342 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": 962679, "vin": [ { "gen": { "height": 962669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5797c2767fb32a1bc26acb2380c1ceb284b22b30d1b4f9e5881708a375ab1e1" } } ], "extra": [ 1, 218, 99, 244, 154, 27, 56, 54, 128, 78, 229, 102, 249, 152, 120, 219, 199, 100, 28, 186, 6, 97, 123, 198, 122, 73, 26, 112, 59, 124, 5, 247, 34, 2, 17, 0, 0, 0, 12, 0, 17, 5, 91, 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