Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f765699d7c8940aff59fa6590226c0e61f7c77768c64afae2e6c536957e3c089

Tx prefix hash: 572f36585ebe731f46b4564b606a08628432a25be45c4a3b29bb59c136e091d6
Tx public key: 792fbe4eee71bc51b8b440c87f82d9c0d162e0725f47098479ec14f0272f28ba
Timestamp: 1731700872 Timestamp [UCT]: 2024-11-15 20:01:12 Age [y:d:h:m:s]: 00:008:09:35:43
Block: 1154463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6015 RingCT/type: yes/0
Extra: 01792fbe4eee71bc51b8b440c87f82d9c0d162e0725f47098479ec14f0272f28ba021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfccdc8afa04810a4124d4c9c5d7799413f0b85f41b95acbdd4b7a9d8c54cd5d 0.600000000000 1640076 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": 1154473, "vin": [ { "gen": { "height": 1154463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfccdc8afa04810a4124d4c9c5d7799413f0b85f41b95acbdd4b7a9d8c54cd5d" } } ], "extra": [ 1, 121, 47, 190, 78, 238, 113, 188, 81, 184, 180, 64, 200, 127, 130, 217, 192, 209, 98, 224, 114, 95, 71, 9, 132, 121, 236, 20, 240, 39, 47, 40, 186, 2, 17, 0, 0, 0, 5, 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