Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 397fb3ee8dd0498f6e5c2a538551bc047cf97daefd8a07940c04b6351d9fe92e

Tx prefix hash: 03fccdb15604a170b9eaf007fcb97c9d5ee5710f9dedcfdaf98d56c127518ad2
Tx public key: 844f9dcccc179def9f79130daab2f4ca50e40e98154b0a1b472d079df71046ba
Timestamp: 1710892540 Timestamp [UCT]: 2024-03-19 23:55:40 Age [y:d:h:m:s]: 01:035:06:55:09
Block: 982069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286196 RingCT/type: yes/0
Extra: 01844f9dcccc179def9f79130daab2f4ca50e40e98154b0a1b472d079df71046ba02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdfb86c196d84ff1bbf746efe0b1613d5e7b27833bc348070307a5f21695ed4e 0.600000000000 1442172 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": 982079, "vin": [ { "gen": { "height": 982069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdfb86c196d84ff1bbf746efe0b1613d5e7b27833bc348070307a5f21695ed4e" } } ], "extra": [ 1, 132, 79, 157, 204, 204, 23, 157, 239, 159, 121, 19, 13, 170, 178, 244, 202, 80, 228, 14, 152, 21, 75, 10, 27, 71, 45, 7, 157, 247, 16, 70, 186, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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