Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d317c57bdd746a14a513431a8d71c717da99780474ee3e6f13a582f38710ecfe

Tx prefix hash: 713444d43d41f3e65bfba5e747da7d16de25506896fcd472109a616162d1ebcd
Tx public key: a92c28046e90c7f8def6a031483a706fe308906dbe4e8bbd3f689d51f0271a9f
Timestamp: 1732683057 Timestamp [UCT]: 2024-11-27 04:50:57 Age [y:d:h:m:s]: 00:128:02:20:16
Block: 1162606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91363 RingCT/type: yes/0
Extra: 01a92c28046e90c7f8def6a031483a706fe308906dbe4e8bbd3f689d51f0271a9f0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23ab942a9278e29d6d12b1392eb998b8d4e19e40073ae11f3348a0485cc52cdb 0.600000000000 1648263 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": 1162616, "vin": [ { "gen": { "height": 1162606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23ab942a9278e29d6d12b1392eb998b8d4e19e40073ae11f3348a0485cc52cdb" } } ], "extra": [ 1, 169, 44, 40, 4, 110, 144, 199, 248, 222, 246, 160, 49, 72, 58, 112, 111, 227, 8, 144, 109, 190, 78, 139, 189, 63, 104, 157, 81, 240, 39, 26, 159, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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