Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2428d9712a1bfb7c4ed52283ab49a3a13aa649c003001a6e41fc7a3f9e488cab

Tx prefix hash: 4ec7b1e9c53e9b6a4972f88b0b439374882c6070a1b7e45e092238ac0548225c
Tx public key: 0fa0b8c790bf9900c2f287793b07832095cf459523e7caae8918ebc2dd53f0db
Timestamp: 1746430330 Timestamp [UCT]: 2025-05-05 07:32:10 Age [y:d:h:m:s]: 00:192:04:53:54
Block: 1276149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135078 RingCT/type: yes/0
Extra: 010fa0b8c790bf9900c2f287793b07832095cf459523e7caae8918ebc2dd53f0db0211000000011f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef1572d82d449b3c31739bdb503d10bf67d17e1cda85b8026ab52a67cd0caf3f 0.600000000000 1763472 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": 1276159, "vin": [ { "gen": { "height": 1276149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef1572d82d449b3c31739bdb503d10bf67d17e1cda85b8026ab52a67cd0caf3f" } } ], "extra": [ 1, 15, 160, 184, 199, 144, 191, 153, 0, 194, 242, 135, 121, 59, 7, 131, 32, 149, 207, 69, 149, 35, 231, 202, 174, 137, 24, 235, 194, 221, 83, 240, 219, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 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