Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d67d706e026348bc831d924f70ab31b84c70362658fa7b4d2f8d59671edbe64

Tx prefix hash: 8abfe68b5dd196f3a4baca99b91c808d09c07afeec991e7efe4ad5bbd7377a83
Tx public key: 0f58716da97097654813b63d769ed684504d24c8bfa13c8441f50c69fdcef4d0
Timestamp: 1706201321 Timestamp [UCT]: 2024-01-25 16:48:41 Age [y:d:h:m:s]: 01:031:04:28:37
Block: 943131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283347 RingCT/type: yes/0
Extra: 010f58716da97097654813b63d769ed684504d24c8bfa13c8441f50c69fdcef4d002110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f04fdabdf8dad79373cf5c21da3b02021141c322df35b59ffb0fd0bbc812d62a 0.600000000000 1401331 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": 943141, "vin": [ { "gen": { "height": 943131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f04fdabdf8dad79373cf5c21da3b02021141c322df35b59ffb0fd0bbc812d62a" } } ], "extra": [ 1, 15, 88, 113, 109, 169, 112, 151, 101, 72, 19, 182, 61, 118, 158, 214, 132, 80, 77, 36, 200, 191, 161, 60, 132, 65, 245, 12, 105, 253, 206, 244, 208, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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