Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 232726d867eb5c928e4c3f24c77cef9c4d265148e3e66f1e3f599d2c676b8b72

Tx prefix hash: 80fb9288ba5f3da6ea487ee6fcd4a81c786ba15d36624a3e74e00bd34673a577
Tx public key: dd53cbb32774d1aee8cb29a8bbc6d81a9577aa97a4fbb68868e856e3aa7a7dc1
Timestamp: 1694982249 Timestamp [UCT]: 2023-09-17 20:24:09 Age [y:d:h:m:s]: 01:128:10:25:00
Block: 850335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353066 RingCT/type: yes/0
Extra: 01dd53cbb32774d1aee8cb29a8bbc6d81a9577aa97a4fbb68868e856e3aa7a7dc102110000000975e3f0e9000000000000000000

1 output(s) for total of 0.934301853000 dcy

stealth address amount amount idx
00: 37283907000720c8dfb394662a3036cd873f701f10f033b61774ee8ac93c6817 0.934301853000 1304049 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": 850345, "vin": [ { "gen": { "height": 850335 } } ], "vout": [ { "amount": 934301853, "target": { "key": "37283907000720c8dfb394662a3036cd873f701f10f033b61774ee8ac93c6817" } } ], "extra": [ 1, 221, 83, 203, 179, 39, 116, 209, 174, 232, 203, 41, 168, 187, 198, 216, 26, 149, 119, 170, 151, 164, 251, 182, 136, 104, 232, 86, 227, 170, 122, 125, 193, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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