Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a35db9277ba40194746efdc25bb81922c2b0f911d127b206d583308661adb27b

Tx prefix hash: 1449f94e414e2be60a40dd488d49c83df82a3cb8741980e74343b10d9eb8b03f
Tx public key: 46a996d382bb12e404a9d4828f191c7a7ac590631d1768a92303cfb5b9119377
Timestamp: 1724378927 Timestamp [UCT]: 2024-08-23 02:08:47 Age [y:d:h:m:s]: 00:299:00:25:06
Block: 1093874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213482 RingCT/type: yes/0
Extra: 0146a996d382bb12e404a9d4828f191c7a7ac590631d1768a92303cfb5b9119377021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47d9066fd3c9a1536c718bd4dcf4cb7f2231f7389e586b836867adb83a52adc5 0.600000000000 1568905 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": 1093884, "vin": [ { "gen": { "height": 1093874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47d9066fd3c9a1536c718bd4dcf4cb7f2231f7389e586b836867adb83a52adc5" } } ], "extra": [ 1, 70, 169, 150, 211, 130, 187, 18, 228, 4, 169, 212, 130, 143, 25, 28, 122, 122, 197, 144, 99, 29, 23, 104, 169, 35, 3, 207, 181, 185, 17, 147, 119, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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