Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c579b8708b6f366ab8bf78da7f3e28602e36ce55b5c2515eadf7074242b4340

Tx prefix hash: 7fdb51a1494823e2bfd54c33e476aaab9c9bce6c2112a5b42e1ffab5054ed3c4
Tx public key: 1abe939782575b4caf8119c8f6de6f6e31954776105fff5b0a7243073e32d39d
Timestamp: 1716810737 Timestamp [UCT]: 2024-05-27 11:52:17 Age [y:d:h:m:s]: 00:180:09:32:35
Block: 1031130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129102 RingCT/type: yes/0
Extra: 011abe939782575b4caf8119c8f6de6f6e31954776105fff5b0a7243073e32d39d0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd1471fc6a557aba7b421c9746b9b11cd89e2b4147c0f9d7d1e25a080fc50078 0.600000000000 1499499 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": 1031140, "vin": [ { "gen": { "height": 1031130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd1471fc6a557aba7b421c9746b9b11cd89e2b4147c0f9d7d1e25a080fc50078" } } ], "extra": [ 1, 26, 190, 147, 151, 130, 87, 91, 76, 175, 129, 25, 200, 246, 222, 111, 110, 49, 149, 71, 118, 16, 95, 255, 91, 10, 114, 67, 7, 62, 50, 211, 157, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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