Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca5845b3e3f2172088ba5c7dc0adf12df2f7c40afe818da7d8c81454c0d18dc1

Tx prefix hash: 35eb655b3da6afc8aa3933824a9ef70d302d491e5fa1f3fb9e737d509aa9c417
Tx public key: ffd7add69df7300d967dbf52e0c2c13bb34fbd3fed9aea992de535595fc5e6bb
Timestamp: 1702243763 Timestamp [UCT]: 2023-12-10 21:29:23 Age [y:d:h:m:s]: 01:137:00:25:46
Block: 910347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359080 RingCT/type: yes/0
Extra: 01ffd7add69df7300d967dbf52e0c2c13bb34fbd3fed9aea992de535595fc5e6bb02110000000de6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d8b1a2d2e87e088e8b5f78febf9880884bf33fa292cc453016c150f174458ed 0.600000000000 1367498 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": 910357, "vin": [ { "gen": { "height": 910347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d8b1a2d2e87e088e8b5f78febf9880884bf33fa292cc453016c150f174458ed" } } ], "extra": [ 1, 255, 215, 173, 214, 157, 247, 48, 13, 150, 125, 191, 82, 224, 194, 193, 59, 179, 79, 189, 63, 237, 154, 234, 153, 45, 229, 53, 89, 95, 197, 230, 187, 2, 17, 0, 0, 0, 13, 230, 210, 127, 156, 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