Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17cd44618c759419b0bfec41f8d324ac04a5857b9e6366f4fab43a808986145d

Tx prefix hash: 7f6a147675bf0057ebfdb11538b7447c63b2129324bdd8d99c5e75d184845d81
Tx public key: 053a1948f5ad77ba8cbf078518a5e12d5a9f7ae357bb297a8c493a850b8d9680
Timestamp: 1737230964 Timestamp [UCT]: 2025-01-18 20:09:24 Age [y:d:h:m:s]: 00:305:23:13:06
Block: 1200219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216222 RingCT/type: yes/0
Extra: 01053a1948f5ad77ba8cbf078518a5e12d5a9f7ae357bb297a8c493a850b8d9680021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ffa324f1343814f4f5834e839362ae3da419bf0112c3b953b983ea6337e4b5e 0.600000000000 1686862 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": 1200229, "vin": [ { "gen": { "height": 1200219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ffa324f1343814f4f5834e839362ae3da419bf0112c3b953b983ea6337e4b5e" } } ], "extra": [ 1, 5, 58, 25, 72, 245, 173, 119, 186, 140, 191, 7, 133, 24, 165, 225, 45, 90, 159, 122, 227, 87, 187, 41, 122, 140, 73, 58, 133, 11, 141, 150, 128, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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